Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3213d3d9c2ebc5b4dd0294ebaa6f13eb0bd1483201f4b7d558f4fcacebf10670

Tx prefix hash: b889e7e83cd63bd856fdf14db631b62502e81dcf6530c471e7e6e833626c036b
Tx public key: 576a4b792d6e092c0eef1dec02cb0d885fbd6fd8b6689c0cf12045018d325353
Timestamp: 1737330176 Timestamp [UCT]: 2025-01-19 23:42:56 Age [y:d:h:m:s]: 00:337:04:37:22
Block: 1201031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238587 RingCT/type: yes/0
Extra: 01576a4b792d6e092c0eef1dec02cb0d885fbd6fd8b6689c0cf12045018d325353021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a56fdb6681e63be12ec253ffd70889ee82ab46a0c5f25176dfbd8566fbee460d 0.600000000000 1687678 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": 1201041, "vin": [ { "gen": { "height": 1201031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a56fdb6681e63be12ec253ffd70889ee82ab46a0c5f25176dfbd8566fbee460d" } } ], "extra": [ 1, 87, 106, 75, 121, 45, 110, 9, 44, 14, 239, 29, 236, 2, 203, 13, 136, 95, 189, 111, 216, 182, 104, 156, 12, 241, 32, 69, 1, 141, 50, 83, 83, 2, 17, 0, 0, 0, 5, 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