Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4caf628fda7ce5cdb8bd2427ae53272418052c0ae2a6a47f69ac41922abb020

Tx prefix hash: 4759890c917df3657c5389f7024c7e6073685ba63d2c134599dc74b72eb1d294
Tx public key: 1aa8dae925d56299be1f78b8403e7a7b4ce00153fb712898315d10541317b14e
Timestamp: 1722483121 Timestamp [UCT]: 2024-08-01 03:32:01 Age [y:d:h:m:s]: 00:179:22:20:09
Block: 1078137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128484 RingCT/type: yes/0
Extra: 011aa8dae925d56299be1f78b8403e7a7b4ce00153fb712898315d10541317b14e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38420fc72c22c61625696ba0e1454c180602c88da75777dd9b1bd8c801d14d35 0.600000000000 1550704 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": 1078147, "vin": [ { "gen": { "height": 1078137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38420fc72c22c61625696ba0e1454c180602c88da75777dd9b1bd8c801d14d35" } } ], "extra": [ 1, 26, 168, 218, 233, 37, 213, 98, 153, 190, 31, 120, 184, 64, 62, 122, 123, 76, 224, 1, 83, 251, 113, 40, 152, 49, 93, 16, 84, 19, 23, 177, 78, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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