Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae137c1a7696c57d95432d4d94c8c26567dc84cbe00a8593c807dc64eeab5eb0

Tx prefix hash: 803379a93325c7c9225538963790e9dc78677c39cff8aea4af85091a0c63ea3e
Tx public key: d256fbbf54a12ee5891f047f3f613ed5375ed799bbc43746e83e62ee3a924508
Timestamp: 1717989931 Timestamp [UCT]: 2024-06-10 03:25:31 Age [y:d:h:m:s]: 00:213:08:24:50
Block: 1040895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152682 RingCT/type: yes/0
Extra: 01d256fbbf54a12ee5891f047f3f613ed5375ed799bbc43746e83e62ee3a9245080211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c4e7cabcf19bbffc1d59323887a958f2cddd319e840622430f9d9797ae897c9 0.600000000000 1509558 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": 1040905, "vin": [ { "gen": { "height": 1040895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c4e7cabcf19bbffc1d59323887a958f2cddd319e840622430f9d9797ae897c9" } } ], "extra": [ 1, 210, 86, 251, 191, 84, 161, 46, 229, 137, 31, 4, 127, 63, 97, 62, 213, 55, 94, 215, 153, 187, 196, 55, 70, 232, 62, 98, 238, 58, 146, 69, 8, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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