Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 452a43fbb40354d5e8928cc6ec8d3112a28eed3908d900d9059c1afcffa70f9e

Tx prefix hash: 65e77d129b9fa2cb848941c9fe9bce17fdfed5faab5c71c4bd70d8205c743a94
Tx public key: 7c4d8f7258cd941493633c8169c5a742cd81fd1c395fd4ba5b4d0091264561ad
Timestamp: 1716938090 Timestamp [UCT]: 2024-05-28 23:14:50 Age [y:d:h:m:s]: 00:304:16:12:10
Block: 1032176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217744 RingCT/type: yes/0
Extra: 017c4d8f7258cd941493633c8169c5a742cd81fd1c395fd4ba5b4d0091264561ad02110000000a41ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16a32c19f947785ae791b5dc504810b4a2e159ad73cbe65e8bcf28b96417904c 0.600000000000 1500625 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": 1032186, "vin": [ { "gen": { "height": 1032176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16a32c19f947785ae791b5dc504810b4a2e159ad73cbe65e8bcf28b96417904c" } } ], "extra": [ 1, 124, 77, 143, 114, 88, 205, 148, 20, 147, 99, 60, 129, 105, 197, 167, 66, 205, 129, 253, 28, 57, 95, 212, 186, 91, 77, 0, 145, 38, 69, 97, 173, 2, 17, 0, 0, 0, 10, 65, 238, 28, 155, 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