Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc05c1327d5760592b65d29ee4f5be43639b1ee0ca4428de21ea239033ebd977

Tx prefix hash: f32c85f5adcf50e0bae32fc3b6fc70ccecd38c48972dd3d66549e642b47c9cbd
Tx public key: 6923909217bb3f73e6a3270f613271f8a3dd4117f3dfe3964aa0a2b078fd461a
Timestamp: 1751290664 Timestamp [UCT]: 2025-06-30 13:37:44 Age [y:d:h:m:s]: 00:215:02:30:33
Block: 1315873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151850 RingCT/type: yes/0
Extra: 016923909217bb3f73e6a3270f613271f8a3dd4117f3dfe3964aa0a2b078fd461a02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68c73dbcbe20b13679f8e993209986e8a8ac472ea6df59228e842089bd6f185a 0.600000000000 1803530 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": 1315883, "vin": [ { "gen": { "height": 1315873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68c73dbcbe20b13679f8e993209986e8a8ac472ea6df59228e842089bd6f185a" } } ], "extra": [ 1, 105, 35, 144, 146, 23, 187, 63, 115, 230, 163, 39, 15, 97, 50, 113, 248, 163, 221, 65, 23, 243, 223, 227, 150, 74, 160, 162, 176, 120, 253, 70, 26, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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