Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ecdb3bb3bf6b93932005f2beb5de99d28ea0835f3852099ab412e963d1f9c5f

Tx prefix hash: 7c2918352c47cde7ae2e735dc5371627189cb1ad47f1279a3e64773b30565df2
Tx public key: 066db4d708cd6bd1b7c8da77a9abb02dfdb1027a6e43bc3d54e2cb391d49a986
Timestamp: 1764038945 Timestamp [UCT]: 2025-11-25 02:49:05 Age [y:d:h:m:s]: 00:032:23:54:20
Block: 1419532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23635 RingCT/type: yes/0
Extra: 01066db4d708cd6bd1b7c8da77a9abb02dfdb1027a6e43bc3d54e2cb391d49a9860211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb738c2f9059ab84cc9df2526a3c747fa9552b75bbbbe0d2badb0608839376e 0.600000000000 1908069 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": 1419542, "vin": [ { "gen": { "height": 1419532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb738c2f9059ab84cc9df2526a3c747fa9552b75bbbbe0d2badb0608839376e" } } ], "extra": [ 1, 6, 109, 180, 215, 8, 205, 107, 209, 183, 200, 218, 119, 169, 171, 176, 45, 253, 177, 2, 122, 110, 67, 188, 61, 84, 226, 203, 57, 29, 73, 169, 134, 2, 17, 0, 0, 0, 1, 140, 235, 127, 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