Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8596f5c21f6aafc93650096b0e45c9be16cac0b51014ba0d0a411836418da13

Tx prefix hash: d36045d16d6940defe723489d8de4a0efd16f4912c33615defb84d86f203f53b
Tx public key: e8cdb3c3e133f993f80f69e6f3354cb14e9e08ace4e8df3a6a951b31b0dfe6ea
Timestamp: 1707851919 Timestamp [UCT]: 2024-02-13 19:18:39 Age [y:d:h:m:s]: 01:107:11:48:45
Block: 956840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337904 RingCT/type: yes/0
Extra: 01e8cdb3c3e133f993f80f69e6f3354cb14e9e08ace4e8df3a6a951b31b0dfe6ea02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae867a2d5bdf498c3ec94ed846652daf22df42639f1f661cd6e35574ab30c4c 0.600000000000 1416150 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": 956850, "vin": [ { "gen": { "height": 956840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae867a2d5bdf498c3ec94ed846652daf22df42639f1f661cd6e35574ab30c4c" } } ], "extra": [ 1, 232, 205, 179, 195, 225, 51, 249, 147, 248, 15, 105, 230, 243, 53, 76, 177, 78, 158, 8, 172, 228, 232, 223, 58, 106, 149, 27, 49, 176, 223, 230, 234, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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