Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6520da1f3cf391394ca2fe3076c16c80de37fdeb0cc8b09ac2f225b69b9f142f

Tx prefix hash: b7820b87214b2d97644986431152bbd9e1590dc251001b8ba7681840523e30ab
Tx public key: fed0e42b7a6c24266bcf6ea9d754c399ad50e1873bfe792c898a86e29a653d2b
Timestamp: 1699599298 Timestamp [UCT]: 2023-11-10 06:54:58 Age [y:d:h:m:s]: 01:147:02:59:44
Block: 888428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366334 RingCT/type: yes/0
Extra: 01fed0e42b7a6c24266bcf6ea9d754c399ad50e1873bfe792c898a86e29a653d2b021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.698665394000 dcy

stealth address amount amount idx
00: 88721cfd6cb786df0449543b74154aedab5f6dedd809a55373ab37dd2dcb0242 0.698665394000 1344367 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": 888438, "vin": [ { "gen": { "height": 888428 } } ], "vout": [ { "amount": 698665394, "target": { "key": "88721cfd6cb786df0449543b74154aedab5f6dedd809a55373ab37dd2dcb0242" } } ], "extra": [ 1, 254, 208, 228, 43, 122, 108, 36, 38, 107, 207, 110, 169, 215, 84, 195, 153, 173, 80, 225, 135, 59, 254, 121, 44, 137, 138, 134, 226, 154, 101, 61, 43, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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