Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c040b77df97eed6f70b377ad99bd8aa26acb9f50d0febb6fd20c82b194ca7d76

Tx prefix hash: 5688361ee36ff52bf74da53c48e7ba70ae5bb2f0caaa764d44cee90485d3ee37
Tx public key: b1c4f404b2e29c0c2e50fd8310cb7d07ef82a80468767ef955b0c20914764429
Timestamp: 1710024227 Timestamp [UCT]: 2024-03-09 22:43:47 Age [y:d:h:m:s]: 01:242:03:26:54
Block: 974853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431765 RingCT/type: yes/0
Extra: 01b1c4f404b2e29c0c2e50fd8310cb7d07ef82a80468767ef955b0c2091476442902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6933c582807b11f7fc73b78a536ca4c65c125847dae301dcd1758c76c94fede1 0.600000000000 1434820 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": 974863, "vin": [ { "gen": { "height": 974853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6933c582807b11f7fc73b78a536ca4c65c125847dae301dcd1758c76c94fede1" } } ], "extra": [ 1, 177, 196, 244, 4, 178, 226, 156, 12, 46, 80, 253, 131, 16, 203, 125, 7, 239, 130, 168, 4, 104, 118, 126, 249, 85, 176, 194, 9, 20, 118, 68, 41, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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