Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1414c81486f752f6a626e1b103a582d736515e3845a29f2b3967eb559da30d3b

Tx prefix hash: 7d21746a24bacc6e293bd0551248cc40e677693fbfab0de337bd83942901aa7a
Tx public key: 6ee0156c84e434a277e2758b75c1c75ee618aa9e2a7aaf82f9796f2f710f69f4
Timestamp: 1764701787 Timestamp [UCT]: 2025-12-02 18:56:27 Age [y:d:h:m:s]: 00:003:00:49:25
Block: 1425028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2162 RingCT/type: yes/0
Extra: 016ee0156c84e434a277e2758b75c1c75ee618aa9e2a7aaf82f9796f2f710f69f4021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40311ef23bfb54d2ce780f3d0b5c9d8f735ee112ba3319177a8ce48e1796f409 0.600000000000 1913661 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": 1425038, "vin": [ { "gen": { "height": 1425028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40311ef23bfb54d2ce780f3d0b5c9d8f735ee112ba3319177a8ce48e1796f409" } } ], "extra": [ 1, 110, 224, 21, 108, 132, 228, 52, 162, 119, 226, 117, 139, 117, 193, 199, 94, 230, 24, 170, 158, 42, 122, 175, 130, 249, 121, 111, 47, 113, 15, 105, 244, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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