Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebecf52d160cfb40d7b03d1b54269a4c475d19d95d1bcfbbf2d84a25472d059

Tx prefix hash: 9ff28f0a170b7e4f399417d1ca2bdcf12d076f551ca1e1f10fe0bccaeb37834e
Tx public key: b6404526278f11ff1e1996dba5e76ee971b8ccf1d9e582d5561f3bf467994ac5
Timestamp: 1698623106 Timestamp [UCT]: 2023-10-29 23:45:06 Age [y:d:h:m:s]: 01:345:08:39:00
Block: 880546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505498 RingCT/type: yes/0
Extra: 01b6404526278f11ff1e1996dba5e76ee971b8ccf1d9e582d5561f3bf467994ac5021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.741968695000 dcy

stealth address amount amount idx
00: 8d01a007d4de49361eb43b67744183692f9b63194aaa40bd54a37cff2866dce9 0.741968695000 1336104 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": 880556, "vin": [ { "gen": { "height": 880546 } } ], "vout": [ { "amount": 741968695, "target": { "key": "8d01a007d4de49361eb43b67744183692f9b63194aaa40bd54a37cff2866dce9" } } ], "extra": [ 1, 182, 64, 69, 38, 39, 143, 17, 255, 30, 25, 150, 219, 165, 231, 110, 233, 113, 184, 204, 241, 217, 229, 130, 213, 86, 31, 59, 244, 103, 153, 74, 197, 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