Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7959868d99fb6231a4d3eed8c72b888d533ed4e58dd536af6a592d26661cb21b

Tx prefix hash: dddaa43fa5c44986cacb079f8fb02091fe503e73949662af8d4be4ae419ba475
Tx public key: e0659bc1b0080e533f6380a06176a197d9a2d2cd68c5d35080f2cb239c384053
Timestamp: 1723574538 Timestamp [UCT]: 2024-08-13 18:42:18 Age [y:d:h:m:s]: 00:275:19:50:01
Block: 1087196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197032 RingCT/type: yes/0
Extra: 01e0659bc1b0080e533f6380a06176a197d9a2d2cd68c5d35080f2cb239c38405302110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1831a082d8e34c27e00fc1b9f2ffccc727eda665ac0da283786b46890eaa891d 0.600000000000 1561801 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": 1087206, "vin": [ { "gen": { "height": 1087196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1831a082d8e34c27e00fc1b9f2ffccc727eda665ac0da283786b46890eaa891d" } } ], "extra": [ 1, 224, 101, 155, 193, 176, 8, 14, 83, 63, 99, 128, 160, 97, 118, 161, 151, 217, 162, 210, 205, 104, 197, 211, 80, 128, 242, 203, 35, 156, 56, 64, 83, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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