Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4aabb10652b53639fc4c29c71807792284e76d7fd2b7f99b69e440987c9b9f

Tx prefix hash: 186273e7892edd92c763568d593e4685df48b9e6f2e3ce239e928083e4c2fe12
Tx public key: c0d1048f870ab9e1f21865054b24aafbd49c1efb49f2a26501fb507c891573c9
Timestamp: 1724728260 Timestamp [UCT]: 2024-08-27 03:11:00 Age [y:d:h:m:s]: 00:291:07:24:46
Block: 1096745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208038 RingCT/type: yes/0
Extra: 01c0d1048f870ab9e1f21865054b24aafbd49c1efb49f2a26501fb507c891573c9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56ab6a4886090e259b92886a11293da2d521cbcfb9d634ede4a7e34267f7fb3e 0.600000000000 1571940 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": 1096755, "vin": [ { "gen": { "height": 1096745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56ab6a4886090e259b92886a11293da2d521cbcfb9d634ede4a7e34267f7fb3e" } } ], "extra": [ 1, 192, 209, 4, 143, 135, 10, 185, 225, 242, 24, 101, 5, 75, 36, 170, 251, 212, 156, 30, 251, 73, 242, 162, 101, 1, 251, 80, 124, 137, 21, 115, 201, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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