Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83db870dfd3ebc915c120ac23c0a22b108fb6db6886d90851fde5c60f6a8df6e

Tx prefix hash: d5dadcd5c566f8091d5d0505b7f32e8389c272542a5b2b2e4b96a1f5800ee72b
Tx public key: a1edf35fca587b558bd405260a6b9f72bb1ddc0f27f3cda56d201028ab94dafe
Timestamp: 1733384837 Timestamp [UCT]: 2024-12-05 07:47:17 Age [y:d:h:m:s]: 00:330:07:26:26
Block: 1168417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233591 RingCT/type: yes/0
Extra: 01a1edf35fca587b558bd405260a6b9f72bb1ddc0f27f3cda56d201028ab94dafe0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6b136541c7603713ccc73d37ef6c6f34a5d537050dd1c127966bb46fa1cd975 0.600000000000 1654126 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": 1168427, "vin": [ { "gen": { "height": 1168417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b136541c7603713ccc73d37ef6c6f34a5d537050dd1c127966bb46fa1cd975" } } ], "extra": [ 1, 161, 237, 243, 95, 202, 88, 123, 85, 139, 212, 5, 38, 10, 107, 159, 114, 187, 29, 220, 15, 39, 243, 205, 165, 109, 32, 16, 40, 171, 148, 218, 254, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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