Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b6faef3cc0bc00f2d979c158d6952df4a0be10e61a112b0f13d0ae0b322889

Tx prefix hash: d47cbdcfb7144af48cb615131b127c17ddcb693359898db5ca119fa2d270710b
Tx public key: b4c53c7a02c2a15b4767208deb89f401ac5e5b4367ce3fcb41ec1835b1cf3934
Timestamp: 1731122621 Timestamp [UCT]: 2024-11-09 03:23:41 Age [y:d:h:m:s]: 00:127:04:18:28
Block: 1149684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90727 RingCT/type: yes/0
Extra: 01b4c53c7a02c2a15b4767208deb89f401ac5e5b4367ce3fcb41ec1835b1cf3934021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65da0e9e1984ffc66133031ee87dce5d66689c60e5ccfdf3b1032daf2d9a53d1 0.600000000000 1634823 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": 1149694, "vin": [ { "gen": { "height": 1149684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65da0e9e1984ffc66133031ee87dce5d66689c60e5ccfdf3b1032daf2d9a53d1" } } ], "extra": [ 1, 180, 197, 60, 122, 2, 194, 161, 91, 71, 103, 32, 141, 235, 137, 244, 1, 172, 94, 91, 67, 103, 206, 63, 203, 65, 236, 24, 53, 177, 207, 57, 52, 2, 17, 0, 0, 0, 8, 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