Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 586a4041ad8ec255ceeaf8fe4cae5bafbc95a355cd9274195d70c243dc6fbe31

Tx prefix hash: 82841b0297afefefc1a9586bebab6832c2e96757c2d4a1d019fd57b9bdfb4f49
Tx public key: 32df2c39a94e60491bbe4d5d3945efd18fc83309bedc3fa922c922191ed5fd9b
Timestamp: 1736982530 Timestamp [UCT]: 2025-01-15 23:08:50 Age [y:d:h:m:s]: 00:153:10:18:27
Block: 1198192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109377 RingCT/type: yes/0
Extra: 0132df2c39a94e60491bbe4d5d3945efd18fc83309bedc3fa922c922191ed5fd9b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6f155bdf9a1269a1097341f6f4bf3f058c00e321df5261c9c9358ebe768a4d2 0.600000000000 1684811 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": 1198202, "vin": [ { "gen": { "height": 1198192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6f155bdf9a1269a1097341f6f4bf3f058c00e321df5261c9c9358ebe768a4d2" } } ], "extra": [ 1, 50, 223, 44, 57, 169, 78, 96, 73, 27, 190, 77, 93, 57, 69, 239, 209, 143, 200, 51, 9, 190, 220, 63, 169, 34, 201, 34, 25, 30, 213, 253, 155, 2, 17, 0, 0, 0, 3, 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