Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f28c3edc10d41c5af6dbce2317d40f87a3405f27e914d891ebee5deced7d5d

Tx prefix hash: f0a232bae97da2c91db4b038f59de2ec4fdc10bb1cdf6ec97e80ffda9759a7a6
Tx public key: e6499b4d1b6ef4e4a4e8951e520581f8266782ff6c0a756b7ac6065fbdd84f9b
Timestamp: 1702287975 Timestamp [UCT]: 2023-12-11 09:46:15 Age [y:d:h:m:s]: 01:153:05:23:51
Block: 910717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370663 RingCT/type: yes/0
Extra: 01e6499b4d1b6ef4e4a4e8951e520581f8266782ff6c0a756b7ac6065fbdd84f9b021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 779ce5ce864a43041ae3e20fb4a2ea5181ebafd7848f8d35c260ac2df28f24b6 0.600000000000 1367884 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": 910727, "vin": [ { "gen": { "height": 910717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "779ce5ce864a43041ae3e20fb4a2ea5181ebafd7848f8d35c260ac2df28f24b6" } } ], "extra": [ 1, 230, 73, 155, 77, 27, 110, 244, 228, 164, 232, 149, 30, 82, 5, 129, 248, 38, 103, 130, 255, 108, 10, 117, 107, 122, 198, 6, 95, 189, 216, 79, 155, 2, 17, 0, 0, 0, 3, 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