Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec8ac9de0c6691c879b5e8ddb3352c146d7daa41e86b0f98823c17d0734bf01

Tx prefix hash: 411c1532efa33136ada3eac52bb4408b333d9a7cd581b25b28da1008d81e614c
Tx public key: efcaf4580ebd9ebd22f07ae830bcf0d7b9e5062ed2a62b97235497ce364aecfc
Timestamp: 1713717475 Timestamp [UCT]: 2024-04-21 16:37:55 Age [y:d:h:m:s]: 01:193:04:06:35
Block: 1005464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396708 RingCT/type: yes/0
Extra: 01efcaf4580ebd9ebd22f07ae830bcf0d7b9e5062ed2a62b97235497ce364aecfc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31688de8b31738d8f42ab92353a1a86e569ae8b0336c72f068ec33acd4a234c4 0.600000000000 1466166 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": 1005474, "vin": [ { "gen": { "height": 1005464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31688de8b31738d8f42ab92353a1a86e569ae8b0336c72f068ec33acd4a234c4" } } ], "extra": [ 1, 239, 202, 244, 88, 14, 189, 158, 189, 34, 240, 122, 232, 48, 188, 240, 215, 185, 229, 6, 46, 210, 166, 43, 151, 35, 84, 151, 206, 54, 74, 236, 252, 2, 17, 0, 0, 0, 2, 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