Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a8bba72b02637d4e922bcf502b2dbd4338176ed049a485c326f8e1f4d064a4

Tx prefix hash: 180ce329de65fd9f534ec186a4da54fee43964eab56422a49f82172c4ce0d6f1
Tx public key: cea1ebc33b700c50b40c54864976e9da6f3fd48da5ddd95f217e30ec9fb10745
Timestamp: 1583532407 Timestamp [UCT]: 2020-03-06 22:06:47 Age [y:d:h:m:s]: 05:006:14:37:54
Block: 77731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159965 RingCT/type: yes/0
Extra: 01cea1ebc33b700c50b40c54864976e9da6f3fd48da5ddd95f217e30ec9fb107450211000000014943cd9f000000000000000000

1 output(s) for total of 339.192095228000 dcy

stealth address amount amount idx
00: 279444a2ce9cded8e9a2ae74fd83f26855d554bbc115561830731a8714309e92 339.192095228000 142904 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": 77741, "vin": [ { "gen": { "height": 77731 } } ], "vout": [ { "amount": 339192095228, "target": { "key": "279444a2ce9cded8e9a2ae74fd83f26855d554bbc115561830731a8714309e92" } } ], "extra": [ 1, 206, 161, 235, 195, 59, 112, 12, 80, 180, 12, 84, 134, 73, 118, 233, 218, 111, 63, 212, 141, 165, 221, 217, 95, 33, 126, 48, 236, 159, 177, 7, 69, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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