Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d4a714ae43a523f6c8ab971bfbaabf4b3e608e9999ab59b42051dadc85aaa7

Tx prefix hash: 6395b81cb798d39266d748b6c48424ab7ea2a70ea86448d9eb44058aa8a7c44d
Tx public key: d8e1e9b4c866974198fe9331a07088b5d63ba572462a94c97f45ff549c0b3bc3
Timestamp: 1732350603 Timestamp [UCT]: 2024-11-23 08:30:03 Age [y:d:h:m:s]: 00:000:13:27:52
Block: 1159854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394 RingCT/type: yes/0
Extra: 01d8e1e9b4c866974198fe9331a07088b5d63ba572462a94c97f45ff549c0b3bc30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d97699bf6876e49a7e2f77ac1eff00e825cf5c4922ac98ba00464c4a4fe4b6f9 0.600000000000 1645493 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": 1159864, "vin": [ { "gen": { "height": 1159854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d97699bf6876e49a7e2f77ac1eff00e825cf5c4922ac98ba00464c4a4fe4b6f9" } } ], "extra": [ 1, 216, 225, 233, 180, 200, 102, 151, 65, 152, 254, 147, 49, 160, 112, 136, 181, 214, 59, 165, 114, 70, 42, 148, 201, 127, 69, 255, 84, 156, 11, 59, 195, 2, 17, 0, 0, 0, 4, 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