Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9d7c7ad795bf28f1750bb713a41f689056e88d4675a13be498cb516f86e6aa

Tx prefix hash: fa3edde72cc5bba14956f1ccb8d0e97fecf1eee0c0a835b3403768539dcf747f
Tx public key: 64754aac1c9f2b65bf5a6046a75853850c284e76131560fa306d7e2dd7bdb6b2
Timestamp: 1703560346 Timestamp [UCT]: 2023-12-26 03:12:26 Age [y:d:h:m:s]: 01:150:06:30:19
Block: 921264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368554 RingCT/type: yes/0
Extra: 0164754aac1c9f2b65bf5a6046a75853850c284e76131560fa306d7e2dd7bdb6b2021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7026e821cf95a413bb88d669921dfe39cf60df752b0df366ea9f557cfb0e24b3 0.600000000000 1378950 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": 921274, "vin": [ { "gen": { "height": 921264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7026e821cf95a413bb88d669921dfe39cf60df752b0df366ea9f557cfb0e24b3" } } ], "extra": [ 1, 100, 117, 74, 172, 28, 159, 43, 101, 191, 90, 96, 70, 167, 88, 83, 133, 12, 40, 78, 118, 19, 21, 96, 250, 48, 109, 126, 45, 215, 189, 182, 178, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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