Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e168848b63a9e0fb44c3df5d17b5f7bf1a80b033572a8e9a8dc57df9a3ab0f

Tx prefix hash: 44f94b45e5960c4731222131a27d6f814402438026fbfc73ed23cc3eef8acddf
Tx public key: 939485a343caebd5b9e5cf794ca263d8558c5d0908621cb27ee1301cf1330c53
Timestamp: 1718747456 Timestamp [UCT]: 2024-06-18 21:50:56 Age [y:d:h:m:s]: 00:290:11:23:26
Block: 1047175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207570 RingCT/type: yes/0
Extra: 01939485a343caebd5b9e5cf794ca263d8558c5d0908621cb27ee1301cf1330c530211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0168bb7c5e6afd3149a28c40ddbfcfbaefd48ca33b7deb9c38a42e67e5604fb6 0.600000000000 1516994 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": 1047185, "vin": [ { "gen": { "height": 1047175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0168bb7c5e6afd3149a28c40ddbfcfbaefd48ca33b7deb9c38a42e67e5604fb6" } } ], "extra": [ 1, 147, 148, 133, 163, 67, 202, 235, 213, 185, 229, 207, 121, 76, 162, 99, 216, 85, 140, 93, 9, 8, 98, 28, 178, 126, 225, 48, 28, 241, 51, 12, 83, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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