Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f237ea4a82b8cc00cf3b297a98d0945c5e0d5938871fa785b5149da39bf5c96

Tx prefix hash: 49a2042d070b796bd07eb5768e498fb431508fca2a212511cf3000007672038b
Tx public key: 2391bdf026674e2d2e37cbf538b0bce612dc26bc4a8b073c645e232ccfc7036b
Timestamp: 1738727467 Timestamp [UCT]: 2025-02-05 03:51:07 Age [y:d:h:m:s]: 00:289:20:35:34
Block: 1212382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204925 RingCT/type: yes/0
Extra: 012391bdf026674e2d2e37cbf538b0bce612dc26bc4a8b073c645e232ccfc7036b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf99fad49d04562f1eaa74ec77f7b0c3715c5a794e8c380cbf57fd8b671b8ea 0.600000000000 1699153 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": 1212392, "vin": [ { "gen": { "height": 1212382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf99fad49d04562f1eaa74ec77f7b0c3715c5a794e8c380cbf57fd8b671b8ea" } } ], "extra": [ 1, 35, 145, 189, 240, 38, 103, 78, 45, 46, 55, 203, 245, 56, 176, 188, 230, 18, 220, 38, 188, 74, 139, 7, 60, 100, 94, 35, 44, 207, 199, 3, 107, 2, 17, 0, 0, 0, 2, 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