Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0649d46acae7e38a3e5db45b23e834d7a6a671c37e3a25767cea09be38a57a

Tx prefix hash: 44a4573c691ef1308fe8004722fd316128fa5e53c3749b56fa327c99f23f1e0c
Tx public key: 474e23f655a2343763cdd5e6cc3490d31fe9d70edc19addbb21d82c9e896f501
Timestamp: 1732219487 Timestamp [UCT]: 2024-11-21 20:04:47 Age [y:d:h:m:s]: 00:002:10:00:19
Block: 1158759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1732 RingCT/type: yes/0
Extra: 01474e23f655a2343763cdd5e6cc3490d31fe9d70edc19addbb21d82c9e896f501021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a78d04246eae123ae285bf7b7fda7b3e857a213ce3fb9b99137078829ea52aab 0.600000000000 1644388 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": 1158769, "vin": [ { "gen": { "height": 1158759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78d04246eae123ae285bf7b7fda7b3e857a213ce3fb9b99137078829ea52aab" } } ], "extra": [ 1, 71, 78, 35, 246, 85, 162, 52, 55, 99, 205, 213, 230, 204, 52, 144, 211, 31, 233, 215, 14, 220, 25, 173, 219, 178, 29, 130, 201, 232, 150, 245, 1, 2, 17, 0, 0, 0, 4, 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