Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45704e1aced2f6edb6fbe2dd7647478bc4c4f34a1ea360c7b961e81576651030

Tx prefix hash: f79a947e37bd21ef70e0edd3a6f490438eb55187a6e86ee268ae42762c2d019e
Tx public key: 5029345fd6caa0437d66e42acf5a89f2ec7afda1bc78e5a880601d43d4367086
Timestamp: 1684587533 Timestamp [UCT]: 2023-05-20 12:58:53 Age [y:d:h:m:s]: 01:319:12:50:39
Block: 764225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489570 RingCT/type: yes/0
Extra: 015029345fd6caa0437d66e42acf5a89f2ec7afda1bc78e5a880601d43d4367086021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.802210487000 dcy

stealth address amount amount idx
00: 501aa944a3f21f2585d03ed42a6861be30e3add0f348c07114892217f280a7e6 1.802210487000 1213134 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": 764235, "vin": [ { "gen": { "height": 764225 } } ], "vout": [ { "amount": 1802210487, "target": { "key": "501aa944a3f21f2585d03ed42a6861be30e3add0f348c07114892217f280a7e6" } } ], "extra": [ 1, 80, 41, 52, 95, 214, 202, 160, 67, 125, 102, 228, 42, 207, 90, 137, 242, 236, 122, 253, 161, 188, 120, 229, 168, 128, 96, 29, 67, 212, 54, 112, 134, 2, 17, 0, 0, 0, 4, 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