Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19ed1c9c12a03b5e7c8a4d41889184e3d6dec14be6468f77590b2c5dc3b6ada7

Tx prefix hash: b178ae0dc78a0693f16ab91cb1c76c4f77957ce36fa24e7f6593e3495a3ba0dc
Tx public key: 3ae9b8d1d81186b7a88d435b2def9539638dfb8638f8d51933f139572b7d8f8d
Timestamp: 1708381547 Timestamp [UCT]: 2024-02-19 22:25:47 Age [y:d:h:m:s]: 01:285:10:07:25
Block: 961234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462769 RingCT/type: yes/0
Extra: 013ae9b8d1d81186b7a88d435b2def9539638dfb8638f8d51933f139572b7d8f8d02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b340d3d29adbb6d89575bf06deaba34e2df030a00c8fb6a10cac336dd1603366 0.600000000000 1420841 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": 961244, "vin": [ { "gen": { "height": 961234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b340d3d29adbb6d89575bf06deaba34e2df030a00c8fb6a10cac336dd1603366" } } ], "extra": [ 1, 58, 233, 184, 209, 216, 17, 134, 183, 168, 141, 67, 91, 45, 239, 149, 57, 99, 141, 251, 134, 56, 248, 213, 25, 51, 241, 57, 87, 43, 125, 143, 141, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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