Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f1a8c3c9201a2ca520750bd9740c01827ff0b4c006ca5280ffe77e564f8802

Tx prefix hash: 1e867181bdfe1d6d630a40abd0efa4d78ffd1ad78d1acf688a053f6dead90df3
Tx public key: 0ec127ae0b9a4b8a9ea2451381e7e4780d76571df376f25a2a3a466920997911
Timestamp: 1583379343 Timestamp [UCT]: 2020-03-05 03:35:43 Age [y:d:h:m:s]: 04:301:16:27:47
Block: 76613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110049 RingCT/type: yes/0
Extra: 010ec127ae0b9a4b8a9ea2451381e7e4780d76571df376f25a2a3a46692099791102110000002903d36d11000000000000000000

1 output(s) for total of 342.097674797000 dcy

stealth address amount amount idx
00: 01e414f82bdca237fce0ea4077fa58a4b3dfba59c30cf5b3f29a665a141eefcc 342.097674797000 141014 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": 76623, "vin": [ { "gen": { "height": 76613 } } ], "vout": [ { "amount": 342097674797, "target": { "key": "01e414f82bdca237fce0ea4077fa58a4b3dfba59c30cf5b3f29a665a141eefcc" } } ], "extra": [ 1, 14, 193, 39, 174, 11, 154, 75, 138, 158, 162, 69, 19, 129, 231, 228, 120, 13, 118, 87, 29, 243, 118, 242, 90, 42, 58, 70, 105, 32, 153, 121, 17, 2, 17, 0, 0, 0, 41, 3, 211, 109, 17, 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