Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4aa860d6175def49ccbcaef53a8f18f5808a101bded75cc713b7fef8e5b0b1

Tx prefix hash: 9f8a6d38ef8852ff0e8279569155dc1915713e3b53d2657b686636df1b9089da
Tx public key: de0f96299a10bf0bd4aed325169d645799f70310d0e91d8b24a3e10429323f7e
Timestamp: 1577952347 Timestamp [UCT]: 2020-01-02 08:05:47 Age [y:d:h:m:s]: 05:132:01:07:19
Block: 37036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244170 RingCT/type: yes/0
Extra: 01de0f96299a10bf0bd4aed325169d645799f70310d0e91d8b24a3e10429323f7e02110000002e4ac5aa02000000000000000000

1 output(s) for total of 462.684775705000 dcy

stealth address amount amount idx
00: 3ccbf76c6ef85c1a4d77d857983d56ad88dff191d9cf042c23c85600902b8fe6 462.684775705000 62804 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": 37046, "vin": [ { "gen": { "height": 37036 } } ], "vout": [ { "amount": 462684775705, "target": { "key": "3ccbf76c6ef85c1a4d77d857983d56ad88dff191d9cf042c23c85600902b8fe6" } } ], "extra": [ 1, 222, 15, 150, 41, 154, 16, 191, 11, 212, 174, 211, 37, 22, 157, 100, 87, 153, 247, 3, 16, 208, 233, 29, 139, 36, 163, 225, 4, 41, 50, 63, 126, 2, 17, 0, 0, 0, 46, 74, 197, 170, 2, 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