Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b05cfec00f83a58e9a65724edb6ae77ddf69f32f6302f83bed02039dafdcf2

Tx prefix hash: 6bcd2917052b418532d443b7625014bfcb4940cd7d8f0fc483be6109b6aa7b45
Tx public key: 7fa5e77f2795d6c2caec6a492e2741e0b6635da2e60f3b3bbedf5f477e6dae08
Timestamp: 1710811317 Timestamp [UCT]: 2024-03-19 01:21:57 Age [y:d:h:m:s]: 00:288:11:18:01
Block: 981394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206481 RingCT/type: yes/0
Extra: 017fa5e77f2795d6c2caec6a492e2741e0b6635da2e60f3b3bbedf5f477e6dae0802110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3871c7c0ca68bb771a800879a7bafa19e698c05dba919e82bdd02eec11c16a11 0.600000000000 1441489 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": 981404, "vin": [ { "gen": { "height": 981394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3871c7c0ca68bb771a800879a7bafa19e698c05dba919e82bdd02eec11c16a11" } } ], "extra": [ 1, 127, 165, 231, 127, 39, 149, 214, 194, 202, 236, 106, 73, 46, 39, 65, 224, 182, 99, 93, 162, 230, 15, 59, 59, 190, 223, 95, 71, 126, 109, 174, 8, 2, 17, 0, 0, 0, 14, 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