Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adcb236214f7272954e0c8047762028043b5a824a1351392c59b45ae17029637

Tx prefix hash: 6ab8203773216ef2efc1a8d93c8090171279970fa144d221caad31f5ede57acc
Tx public key: f7e955eede2bc2aa9668f25fe22abd09aec92c65a8f3230df2839125f2c04006
Timestamp: 1673481903 Timestamp [UCT]: 2023-01-12 00:05:03 Age [y:d:h:m:s]: 01:308:01:45:17
Block: 672749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481171 RingCT/type: yes/0
Extra: 01f7e955eede2bc2aa9668f25fe22abd09aec92c65a8f3230df2839125f2c04006021100000002b3e1cbca000000000000000000

1 output(s) for total of 3.621623044000 dcy

stealth address amount amount idx
00: b08612051e94f544ef4ef47efaa3da4d1eac1d4e76d3ff5c7aafc71a9ce5281a 3.621623044000 1114314 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": 672759, "vin": [ { "gen": { "height": 672749 } } ], "vout": [ { "amount": 3621623044, "target": { "key": "b08612051e94f544ef4ef47efaa3da4d1eac1d4e76d3ff5c7aafc71a9ce5281a" } } ], "extra": [ 1, 247, 233, 85, 238, 222, 43, 194, 170, 150, 104, 242, 95, 226, 42, 189, 9, 174, 201, 44, 101, 168, 243, 35, 13, 242, 131, 145, 37, 242, 192, 64, 6, 2, 17, 0, 0, 0, 2, 179, 225, 203, 202, 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