Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31dc37796240301deac383bb48522fedd0c6c0ca9ddd0bf3b68d3e2f82f5c864

Tx prefix hash: 67b26120f494f15727d585fa352f4fa4b866544253f8f02971b12a2a16942775
Tx public key: 0cc401638713f9ad50e888e4a009a9f18cfa5dc033ec83b93f55c9f470ea22a3
Timestamp: 1762482871 Timestamp [UCT]: 2025-11-07 02:34:31 Age [y:d:h:m:s]: 00:081:23:20:15
Block: 1406623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58524 RingCT/type: yes/0
Extra: 010cc401638713f9ad50e888e4a009a9f18cfa5dc033ec83b93f55c9f470ea22a30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 315b433b79588f94400b8309de60d541fb6018dd0e4f2a3dc2edb7cddb497dd9 0.600000000000 1895010 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": 1406633, "vin": [ { "gen": { "height": 1406623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "315b433b79588f94400b8309de60d541fb6018dd0e4f2a3dc2edb7cddb497dd9" } } ], "extra": [ 1, 12, 196, 1, 99, 135, 19, 249, 173, 80, 232, 136, 228, 160, 9, 169, 241, 140, 250, 93, 192, 51, 236, 131, 185, 63, 85, 201, 244, 112, 234, 34, 163, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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