Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f13249449ef6d17764f13acf2f1ccd1b31c9ed606d4f4c33bae9bdfe20c1deef

Tx prefix hash: 0c8ace13f78a0f039075f5527ee621f123cb6640ff031d791eafe3c0e06fbb57
Tx public key: 8129af760ed593974b388209a7fd9e31dd29ccf81684e06166d0e84c052d2f41
Timestamp: 1718686872 Timestamp [UCT]: 2024-06-18 05:01:12 Age [y:d:h:m:s]: 00:309:19:19:11
Block: 1046669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221386 RingCT/type: yes/0
Extra: 018129af760ed593974b388209a7fd9e31dd29ccf81684e06166d0e84c052d2f410211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f6e0ff51fea2ba315c631604c1b278684de5fb1dccb67132a2573e2169e09e6 0.600000000000 1516486 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1046679, "vin": [ { "gen": { "height": 1046669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f6e0ff51fea2ba315c631604c1b278684de5fb1dccb67132a2573e2169e09e6" } } ], "extra": [ 1, 129, 41, 175, 118, 14, 213, 147, 151, 75, 56, 130, 9, 167, 253, 158, 49, 221, 41, 204, 248, 22, 132, 224, 97, 102, 208, 232, 76, 5, 45, 47, 65, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8