Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa05260ee19298e1eb55f2082f99535a9a711d605b1f8d0184deba70c705b13

Tx prefix hash: 0a064243a5cd542a910e325f56c8ce27f411a8c78d9aa4f99b6556a3e8b54111
Tx public key: 1fd926cc7556692318f799453c32b4ed56568dead33c092b94b0ef3d6c33b4ce
Timestamp: 1712780998 Timestamp [UCT]: 2024-04-10 20:29:58 Age [y:d:h:m:s]: 01:067:16:20:41
Block: 997682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309283 RingCT/type: yes/0
Extra: 011fd926cc7556692318f799453c32b4ed56568dead33c092b94b0ef3d6c33b4ce02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dcc4fa822c79e95a25f30d3f49058c808d9ae95cf50c4c0a6f63b11cd3c14ef 0.600000000000 1458116 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": 997692, "vin": [ { "gen": { "height": 997682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dcc4fa822c79e95a25f30d3f49058c808d9ae95cf50c4c0a6f63b11cd3c14ef" } } ], "extra": [ 1, 31, 217, 38, 204, 117, 86, 105, 35, 24, 247, 153, 69, 60, 50, 180, 237, 86, 86, 141, 234, 211, 60, 9, 43, 148, 176, 239, 61, 108, 51, 180, 206, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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