Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4253f2ce692701360d8a1b4b833a851def79d0964fab43976747be574f8e8d25

Tx prefix hash: b3e3bff32024f3c4eb9211bb98ae48afa59e9f10466c60fa4a37d2d182b08ad0
Tx public key: f602fdfaeb19f8d0601016b0ff751dc0ff2379d1cdfa7509e1a2a56171a9e922
Timestamp: 1729667926 Timestamp [UCT]: 2024-10-23 07:18:46 Age [y:d:h:m:s]: 00:141:03:55:35
Block: 1137673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100697 RingCT/type: yes/0
Extra: 01f602fdfaeb19f8d0601016b0ff751dc0ff2379d1cdfa7509e1a2a56171a9e922021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00557b0b0287869292033f193926c609599b883fc527690aae8e8240ab7a5709 0.600000000000 1621208 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": 1137683, "vin": [ { "gen": { "height": 1137673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00557b0b0287869292033f193926c609599b883fc527690aae8e8240ab7a5709" } } ], "extra": [ 1, 246, 2, 253, 250, 235, 25, 248, 208, 96, 16, 22, 176, 255, 117, 29, 192, 255, 35, 121, 209, 205, 250, 117, 9, 225, 162, 165, 97, 113, 169, 233, 34, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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