Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31b44e19e2364c7f59bf1d52e7a687a02983eec3042f2249c04c60b7d45d115

Tx prefix hash: 7e67d5d8e4a73e642031b946f2712a411f283b243bdb709e5bc4ec0f5118a781
Tx public key: 505480be55b2421376dd9a94760b620d300d51426333f8322eb73e86866f61e8
Timestamp: 1693238638 Timestamp [UCT]: 2023-08-28 16:03:58 Age [y:d:h:m:s]: 01:298:06:40:01
Block: 835857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474198 RingCT/type: yes/0
Extra: 01505480be55b2421376dd9a94760b620d300d51426333f8322eb73e86866f61e8021100000005faf35c9c000000000000000000

1 output(s) for total of 1.043419276000 dcy

stealth address amount amount idx
00: 4b5acbe04b6f1fb5b3fe1960117bd2419d54d9096fbe27c7341bcba724a8f9a9 1.043419276000 1288425 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": 835867, "vin": [ { "gen": { "height": 835857 } } ], "vout": [ { "amount": 1043419276, "target": { "key": "4b5acbe04b6f1fb5b3fe1960117bd2419d54d9096fbe27c7341bcba724a8f9a9" } } ], "extra": [ 1, 80, 84, 128, 190, 85, 178, 66, 19, 118, 221, 154, 148, 118, 11, 98, 13, 48, 13, 81, 66, 99, 51, 248, 50, 46, 183, 62, 134, 134, 111, 97, 232, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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