Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15642335f96ce483a383776be4b7e17a06c719d84bfc802cd620f8d4a4de85e6

Tx prefix hash: 5f28017ffeb20522374cec41c85c1220713dfe45ce68541b348c78f0613d78c1
Tx public key: 6d8b68d75ab51f38642b222d26cb8dcf7d40a125a9aa79cda2acdb26281c94e3
Timestamp: 1735449270 Timestamp [UCT]: 2024-12-29 05:14:30 Age [y:d:h:m:s]: 00:310:00:14:28
Block: 1185504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219072 RingCT/type: yes/0
Extra: 016d8b68d75ab51f38642b222d26cb8dcf7d40a125a9aa79cda2acdb26281c94e30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b2bdd3c8af90bb173be0c063c4d628c20cc5d440843e29f03c4cd8442b828ec 0.600000000000 1671977 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": 1185514, "vin": [ { "gen": { "height": 1185504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2bdd3c8af90bb173be0c063c4d628c20cc5d440843e29f03c4cd8442b828ec" } } ], "extra": [ 1, 109, 139, 104, 215, 90, 181, 31, 56, 100, 43, 34, 45, 38, 203, 141, 207, 125, 64, 161, 37, 169, 170, 121, 205, 162, 172, 219, 38, 40, 28, 148, 227, 2, 17, 0, 0, 0, 5, 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