Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a02e870f176d79635f1c9db2f2b7482f9cf229679aca50fb0786aa19b8fe69bb

Tx prefix hash: 25bc4eabe1ae0c47997cade70a729e022115a313146afe2b2cb8f35752d43b38
Tx public key: 7c18767fe2682ba319603dbf7b5c236ede4e83b4c170f4784a6ae6d5a746d293
Timestamp: 1737419393 Timestamp [UCT]: 2025-01-21 00:29:53 Age [y:d:h:m:s]: 00:148:02:06:27
Block: 1201782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105575 RingCT/type: yes/0
Extra: 017c18767fe2682ba319603dbf7b5c236ede4e83b4c170f4784a6ae6d5a746d2930211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b49082e98c46f2b0037e289937970ff990a71c889572d4f4d17c1d2b94316e35 0.600000000000 1688439 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": 1201792, "vin": [ { "gen": { "height": 1201782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b49082e98c46f2b0037e289937970ff990a71c889572d4f4d17c1d2b94316e35" } } ], "extra": [ 1, 124, 24, 118, 127, 226, 104, 43, 163, 25, 96, 61, 191, 123, 92, 35, 110, 222, 78, 131, 180, 193, 112, 244, 120, 74, 106, 230, 213, 167, 70, 210, 147, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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