Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd1ac482675131e09494217f792ef765b4c49eb6fd25534d177f6eb2ae803d1

Tx prefix hash: 8789a522ad5afc17ea2df4f8bc96cae56dd5ece4d584bd74eeed5ac06098e1f8
Tx public key: 6c59d7cf516feadd581eb248828fcc068703a3850c70b10835a552f7c604b6c9
Timestamp: 1763277560 Timestamp [UCT]: 2025-11-16 07:19:20 Age [y:d:h:m:s]: 00:012:02:46:42
Block: 1413216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8681 RingCT/type: yes/0
Extra: 016c59d7cf516feadd581eb248828fcc068703a3850c70b10835a552f7c604b6c90211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851b07665092dd26fe6b7aceb0e2f55d5acb0f1f3f4d5a80a15dd3ed6e2af938 0.600000000000 1901693 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": 1413226, "vin": [ { "gen": { "height": 1413216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851b07665092dd26fe6b7aceb0e2f55d5acb0f1f3f4d5a80a15dd3ed6e2af938" } } ], "extra": [ 1, 108, 89, 215, 207, 81, 111, 234, 221, 88, 30, 178, 72, 130, 143, 204, 6, 135, 3, 163, 133, 12, 112, 177, 8, 53, 165, 82, 247, 198, 4, 182, 201, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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