Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80868dc159e59a6e151f40b6c1068e85e8468bc8b9e21bd7891a9ba2cd6370ab

Tx prefix hash: 7b2ba3606c9de205e1de9dd39fd60b6b9ced0963f11a51e641418aae0a856414
Tx public key: 4a6570826d01863b48ee3f2589317d0f2ec98bdf5a8bdf8cae239d468164ec19
Timestamp: 1696727782 Timestamp [UCT]: 2023-10-08 01:16:22 Age [y:d:h:m:s]: 01:187:01:30:44
Block: 864822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394738 RingCT/type: yes/0
Extra: 014a6570826d01863b48ee3f2589317d0f2ec98bdf5a8bdf8cae239d468164ec19021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.836538136000 dcy

stealth address amount amount idx
00: d5b6280a5f2cbda9587fdbc647d033d1b896ad9e1c9d0b92728299e9d2114d4e 0.836538136000 1319342 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": 864832, "vin": [ { "gen": { "height": 864822 } } ], "vout": [ { "amount": 836538136, "target": { "key": "d5b6280a5f2cbda9587fdbc647d033d1b896ad9e1c9d0b92728299e9d2114d4e" } } ], "extra": [ 1, 74, 101, 112, 130, 109, 1, 134, 59, 72, 238, 63, 37, 137, 49, 125, 15, 46, 201, 139, 223, 90, 139, 223, 140, 174, 35, 157, 70, 129, 100, 236, 25, 2, 17, 0, 0, 0, 5, 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