Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef553dcba9e78f2d03666d333c741084488359957c365538ea6e56a02c5f3009

Tx prefix hash: 512f6122fb036bd37422993b016e94ea529b084003553fdc2d852f02beb878c7
Tx public key: 8c9322a046d3cdf7f3edddc67dc506f16d41f559ae2568aceac4972eb5700c7a
Timestamp: 1703438218 Timestamp [UCT]: 2023-12-24 17:16:58 Age [y:d:h:m:s]: 01:063:12:45:27
Block: 920253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306483 RingCT/type: yes/0
Extra: 018c9322a046d3cdf7f3edddc67dc506f16d41f559ae2568aceac4972eb5700c7a02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14b63911ad67c7b3494123b7cf2d883ce68dde5f8e7b71d0f4eb456f96b55a10 0.600000000000 1377931 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": 920263, "vin": [ { "gen": { "height": 920253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14b63911ad67c7b3494123b7cf2d883ce68dde5f8e7b71d0f4eb456f96b55a10" } } ], "extra": [ 1, 140, 147, 34, 160, 70, 211, 205, 247, 243, 237, 221, 198, 125, 197, 6, 241, 109, 65, 245, 89, 174, 37, 104, 172, 234, 196, 151, 46, 181, 112, 12, 122, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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