Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11548817226cd15396ea75ddfd5b91d838700cb2b1fe6ac1d351feab7a94438d

Tx prefix hash: 580a81b03474bf9f4daa749fcc1ce0c3248436ef5fb36a52dc5561dda0b6d8a4
Tx public key: 21f0581069e5cdad4b36782ea325dc743a9107cf2ad8a3d0d0f5487944b3fc01
Timestamp: 1712638609 Timestamp [UCT]: 2024-04-09 04:56:49 Age [y:d:h:m:s]: 01:025:04:39:36
Block: 996500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278996 RingCT/type: yes/0
Extra: 0121f0581069e5cdad4b36782ea325dc743a9107cf2ad8a3d0d0f5487944b3fc0102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c0dba63e82a2a3bd90d2ff54d962eb27242bd5507536ed9d6878c92226258f1 0.600000000000 1456918 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": 996510, "vin": [ { "gen": { "height": 996500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c0dba63e82a2a3bd90d2ff54d962eb27242bd5507536ed9d6878c92226258f1" } } ], "extra": [ 1, 33, 240, 88, 16, 105, 229, 205, 173, 75, 54, 120, 46, 163, 37, 220, 116, 58, 145, 7, 207, 42, 216, 163, 208, 208, 245, 72, 121, 68, 179, 252, 1, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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