Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c33f792639a48aac9275d0ee88dd31786c606f83125e9e59b262f416e90613

Tx prefix hash: f29860ddf764ed7386ce3d856e30c17825510e40d45a8acb909552ec6368ef16
Tx public key: aa17db331abb5cdb0ddfb34e162d621ae4c04ae644599bc0b4c02de132c9b76a
Timestamp: 1737028496 Timestamp [UCT]: 2025-01-16 11:54:56 Age [y:d:h:m:s]: 00:155:23:56:16
Block: 1198583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111149 RingCT/type: yes/0
Extra: 01aa17db331abb5cdb0ddfb34e162d621ae4c04ae644599bc0b4c02de132c9b76a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d482a5d2b568699e0adaf2a6b17d91edc8550f6e5b6c82e3683d475bbc45b29 0.600000000000 1685208 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": 1198593, "vin": [ { "gen": { "height": 1198583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d482a5d2b568699e0adaf2a6b17d91edc8550f6e5b6c82e3683d475bbc45b29" } } ], "extra": [ 1, 170, 23, 219, 51, 26, 187, 92, 219, 13, 223, 179, 78, 22, 45, 98, 26, 228, 192, 74, 230, 68, 89, 155, 192, 180, 192, 45, 225, 50, 201, 183, 106, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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