Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 099d13ffe754f2c64840146346ef807337e22fdc9d0a68995e385bc0de1eb7b7

Tx prefix hash: f4374fc7a7830cb81752f96a6ae9d8e44fb244e2a7e8e55169eefcd5e7da4eaa
Tx public key: 8944e2b529517c882c096f1e5468133808260e41d171c39fdbcd22d28521f0c1
Timestamp: 1720718103 Timestamp [UCT]: 2024-07-11 17:15:03 Age [y:d:h:m:s]: 00:194:23:55:51
Block: 1063516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139469 RingCT/type: yes/0
Extra: 018944e2b529517c882c096f1e5468133808260e41d171c39fdbcd22d28521f0c102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03e738153e4412e78dfe845a89d6244d29001673ddb1e8d02273a418637dfc9b 0.600000000000 1534031 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": 1063526, "vin": [ { "gen": { "height": 1063516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03e738153e4412e78dfe845a89d6244d29001673ddb1e8d02273a418637dfc9b" } } ], "extra": [ 1, 137, 68, 226, 181, 41, 81, 124, 136, 44, 9, 111, 30, 84, 104, 19, 56, 8, 38, 14, 65, 209, 113, 195, 159, 219, 205, 34, 210, 133, 33, 240, 193, 2, 17, 0, 0, 0, 5, 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