Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcaaac496cdd723daac1e5937a1437ddd35834aa621e29fb648f1581e0bd549f

Tx prefix hash: 350b17efb9bddf638c6be410ddb451cba23b8dcfee54ddb0d64becbce369b319
Tx public key: cb3bde490d6b13b7e2a3d5fe6e8c04985324c6cf6f5bb8a467b0e930a87a9bdd
Timestamp: 1699398278 Timestamp [UCT]: 2023-11-07 23:04:38 Age [y:d:h:m:s]: 01:130:13:05:39
Block: 886764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354500 RingCT/type: yes/0
Extra: 01cb3bde490d6b13b7e2a3d5fe6e8c04985324c6cf6f5bb8a467b0e930a87a9bdd021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.707591745000 dcy

stealth address amount amount idx
00: 438f90ef942906bf116290e2a445e1fe4d51885a50031de6ffa728d7b01ce739 0.707591745000 1342607 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": 886774, "vin": [ { "gen": { "height": 886764 } } ], "vout": [ { "amount": 707591745, "target": { "key": "438f90ef942906bf116290e2a445e1fe4d51885a50031de6ffa728d7b01ce739" } } ], "extra": [ 1, 203, 59, 222, 73, 13, 107, 19, 183, 226, 163, 213, 254, 110, 140, 4, 152, 83, 36, 198, 207, 111, 91, 184, 164, 103, 176, 233, 48, 168, 122, 155, 221, 2, 17, 0, 0, 0, 6, 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