Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba32296a03c5fd395241bf4af7a1fdcff753a9de5c29023ac98933527680d4e5

Tx prefix hash: b741e1237556d4f188a0b404999a8db1b90a5c7410901ab7b9cc604f39c9e3f1
Tx public key: 299d82c69dfeeccde355ff86059aa089d895cefa8870f2d09dc09e68c325246d
Timestamp: 1736410609 Timestamp [UCT]: 2025-01-09 08:16:49 Age [y:d:h:m:s]: 00:162:11:30:30
Block: 1193465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115797 RingCT/type: yes/0
Extra: 01299d82c69dfeeccde355ff86059aa089d895cefa8870f2d09dc09e68c325246d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceecc1e7e39818a34ea892ff0ae36a660842e744d8423069d1de431db531e024 0.600000000000 1680026 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": 1193475, "vin": [ { "gen": { "height": 1193465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceecc1e7e39818a34ea892ff0ae36a660842e744d8423069d1de431db531e024" } } ], "extra": [ 1, 41, 157, 130, 198, 157, 254, 236, 205, 227, 85, 255, 134, 5, 154, 160, 137, 216, 149, 206, 250, 136, 112, 242, 208, 157, 192, 158, 104, 195, 37, 36, 109, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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