Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5eeae80ae12822975b8174422a9668f287df2b9055a5b98479d7163c18a2581

Tx prefix hash: ee1a49a788c73bf5fed0fd7b04ab613606e3084c5b09be9e439b4afc48d21082
Tx public key: 7afcf4da0f6348c6a3fd80da3da295f7b94305dc4849f4faa48d415000e1f1e8
Timestamp: 1755204105 Timestamp [UCT]: 2025-08-14 20:41:45 Age [y:d:h:m:s]: 00:091:09:28:27
Block: 1346814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64941 RingCT/type: yes/0
Extra: 017afcf4da0f6348c6a3fd80da3da295f7b94305dc4849f4faa48d415000e1f1e8021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78cbea5d834b8c33d6383410ca48d1d51cd195e7695b29f38f1c67ef95576625 0.600000000000 1834721 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": 1346824, "vin": [ { "gen": { "height": 1346814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78cbea5d834b8c33d6383410ca48d1d51cd195e7695b29f38f1c67ef95576625" } } ], "extra": [ 1, 122, 252, 244, 218, 15, 99, 72, 198, 163, 253, 128, 218, 61, 162, 149, 247, 185, 67, 5, 220, 72, 73, 244, 250, 164, 141, 65, 80, 0, 225, 241, 232, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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