Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 761cf2f8bbc8ee3a8c2fc8c9052da556b132fb2d4c83f452634124acd421ec0e

Tx prefix hash: 2e89742bb5cb017fc763d2ddf6e3d529349e53145473e5851eb37ac660213eee
Tx public key: 958cf1816aef49f40e9b1859d663e5ebff36571413d4ef6445b501357818e8d1
Timestamp: 1721351980 Timestamp [UCT]: 2024-07-19 01:19:40 Age [y:d:h:m:s]: 00:177:04:19:37
Block: 1068776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126758 RingCT/type: yes/0
Extra: 01958cf1816aef49f40e9b1859d663e5ebff36571413d4ef6445b501357818e8d102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c961e9ba9e1f8847ed5dd0f4d9bf8c8cddf8bbae54d222efdc0b00be7fb1e38 0.600000000000 1539937 of 15

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": 1068786, "vin": [ { "gen": { "height": 1068776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c961e9ba9e1f8847ed5dd0f4d9bf8c8cddf8bbae54d222efdc0b00be7fb1e38" } } ], "extra": [ 1, 149, 140, 241, 129, 106, 239, 73, 244, 14, 155, 24, 89, 214, 99, 229, 235, 255, 54, 87, 20, 19, 212, 239, 100, 69, 181, 1, 53, 120, 24, 232, 209, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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