Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 942592672edef326dc6d5109487be71fc27b5040d8443d8e5c3eb48572a5b056

Tx prefix hash: 88b8ca0382ee40e17f56dfc4089dd4843e8c567e735da852893378372dce7dbc
Tx public key: e402bc1a40c21b5eddb1be6a88f295c06a898d5066aa51ea0eb79ecefdc7a6bb
Timestamp: 1728386247 Timestamp [UCT]: 2024-10-08 11:17:27 Age [y:d:h:m:s]: 00:199:22:40:02
Block: 1127079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142708 RingCT/type: yes/0
Extra: 01e402bc1a40c21b5eddb1be6a88f295c06a898d5066aa51ea0eb79ecefdc7a6bb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3539c11683caa274ab7f10f457ea107d4a7a8ebbd18acefc2aa0e1c28850e982 0.600000000000 1609878 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": 1127089, "vin": [ { "gen": { "height": 1127079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3539c11683caa274ab7f10f457ea107d4a7a8ebbd18acefc2aa0e1c28850e982" } } ], "extra": [ 1, 228, 2, 188, 26, 64, 194, 27, 94, 221, 177, 190, 106, 136, 242, 149, 192, 106, 137, 141, 80, 102, 170, 81, 234, 14, 183, 158, 206, 253, 199, 166, 187, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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