Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f5ee2eb07e161bb89e78dd756b0e10fdcdfd19715ab94454dedef4c0455cb5

Tx prefix hash: 8b9c79c0835db90b467d7b70e561bd89f6ba3bacb4d40873e0074c52c6a53394
Tx public key: e4e8b31f19e9f04e1448e28e2ad0831839517dc83221fb4fbda41f55a468fd48
Timestamp: 1583255612 Timestamp [UCT]: 2020-03-03 17:13:32 Age [y:d:h:m:s]: 04:257:18:37:46
Block: 75884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078339 RingCT/type: yes/0
Extra: 01e4e8b31f19e9f04e1448e28e2ad0831839517dc83221fb4fbda41f55a468fd4802110000005c8a2ee0d9000000000000000000

1 output(s) for total of 344.017541769000 dcy

stealth address amount amount idx
00: d1268d9f2f5255494855e0e7401cc9ab560727c1a34dbc0c76e5f37d29100e13 344.017541769000 139907 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": 75894, "vin": [ { "gen": { "height": 75884 } } ], "vout": [ { "amount": 344017541769, "target": { "key": "d1268d9f2f5255494855e0e7401cc9ab560727c1a34dbc0c76e5f37d29100e13" } } ], "extra": [ 1, 228, 232, 179, 31, 25, 233, 240, 78, 20, 72, 226, 142, 42, 208, 131, 24, 57, 81, 125, 200, 50, 33, 251, 79, 189, 164, 31, 85, 164, 104, 253, 72, 2, 17, 0, 0, 0, 92, 138, 46, 224, 217, 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