Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a928b8ec9b8f3d094c21158983584f91e7a09ebdf3b3529eae7c8a714719c447

Tx prefix hash: 3982516a567dcd0542f625abb1afe55321994b85bb985f31ef77867249634319
Tx public key: 89ade6f7ca599da79ee48c4ea73613b0462a988aee8a4de7c4dea64cfb5ba3b7
Timestamp: 1720370086 Timestamp [UCT]: 2024-07-07 16:34:46 Age [y:d:h:m:s]: 00:264:01:30:57
Block: 1060618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188665 RingCT/type: yes/0
Extra: 0189ade6f7ca599da79ee48c4ea73613b0462a988aee8a4de7c4dea64cfb5ba3b7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b548f588028be9949d6fc0d88d5a8eb802d71bb09b2da842e1d7bafe0315028f 0.600000000000 1531103 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": 1060628, "vin": [ { "gen": { "height": 1060618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b548f588028be9949d6fc0d88d5a8eb802d71bb09b2da842e1d7bafe0315028f" } } ], "extra": [ 1, 137, 173, 230, 247, 202, 89, 157, 167, 158, 228, 140, 78, 167, 54, 19, 176, 70, 42, 152, 138, 238, 138, 77, 231, 196, 222, 166, 76, 251, 91, 163, 183, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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