Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820f3fe02dfd953bf0bd40348c56bb1faa653a18a18a6a2119fc1f78ec97f85b

Tx prefix hash: 1ac11a06d03d91a4938f5ad22c006aeeaf14f6c1e4e31f14596655f1e2c951b0
Tx public key: a3cfb85e665d1c3e2703dab9043f51aecd70e26d59210476bf0d9c889b836f01
Timestamp: 1711826303 Timestamp [UCT]: 2024-03-30 19:18:23 Age [y:d:h:m:s]: 01:004:22:16:13
Block: 989812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264462 RingCT/type: yes/0
Extra: 01a3cfb85e665d1c3e2703dab9043f51aecd70e26d59210476bf0d9c889b836f010211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dea087a2363a6e5f45834cacd6a5918d9fb718b9de9741a23077330a4c3d3b38 0.600000000000 1450130 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": 989822, "vin": [ { "gen": { "height": 989812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dea087a2363a6e5f45834cacd6a5918d9fb718b9de9741a23077330a4c3d3b38" } } ], "extra": [ 1, 163, 207, 184, 94, 102, 93, 28, 62, 39, 3, 218, 185, 4, 63, 81, 174, 205, 112, 226, 109, 89, 33, 4, 118, 191, 13, 156, 136, 155, 131, 111, 1, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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