Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ba58c7fb50177acf5088287bee3cedfbec3f34f478f230ccad4cced95d2ee9

Tx prefix hash: 33f30955575af5fe570df37c6194062788e2f4629197f4fb78b31d63260456fa
Tx public key: 9afac04b0c249d4a36a5bcf6bd5b5efb78aa70e3e194fa4b3e2c3eee60d666fa
Timestamp: 1625653435 Timestamp [UCT]: 2021-07-07 10:23:55 Age [y:d:h:m:s]: 03:143:09:46:19
Block: 289651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872700 RingCT/type: yes/0
Extra: 019afac04b0c249d4a36a5bcf6bd5b5efb78aa70e3e194fa4b3e2c3eee60d666fa0211000000443525d189000000000000000000

1 output(s) for total of 67.341665204000 dcy

stealth address amount amount idx
00: 817defc8931068ce04c4c5fac6eabbf1285aa5b4d80a8dab7e6b9e38448c5e85 67.341665204000 606695 of 0

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": 289661, "vin": [ { "gen": { "height": 289651 } } ], "vout": [ { "amount": 67341665204, "target": { "key": "817defc8931068ce04c4c5fac6eabbf1285aa5b4d80a8dab7e6b9e38448c5e85" } } ], "extra": [ 1, 154, 250, 192, 75, 12, 36, 157, 74, 54, 165, 188, 246, 189, 91, 94, 251, 120, 170, 112, 227, 225, 148, 250, 75, 62, 44, 62, 238, 96, 214, 102, 250, 2, 17, 0, 0, 0, 68, 53, 37, 209, 137, 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