Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1d9606105c6034aace93915f2f49383fc508d23fda6bbc82600921fc11f388b

Tx prefix hash: b8f4307654474941d451103209b70a2d99501979eadef9b2b8e17e255d475a49
Tx public key: 61f2f2b7e416cc54b25924eeae12eae41af3e8c3a2542336886f44d5c73eca42
Timestamp: 1706985064 Timestamp [UCT]: 2024-02-03 18:31:04 Age [y:d:h:m:s]: 01:133:11:48:26
Block: 949637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356418 RingCT/type: yes/0
Extra: 0161f2f2b7e416cc54b25924eeae12eae41af3e8c3a2542336886f44d5c73eca4202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01c1c82363acb1677cc1afee26b9ddd7a9498d1dab6d11c06873b3667db637b 0.600000000000 1408167 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": 949647, "vin": [ { "gen": { "height": 949637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01c1c82363acb1677cc1afee26b9ddd7a9498d1dab6d11c06873b3667db637b" } } ], "extra": [ 1, 97, 242, 242, 183, 228, 22, 204, 84, 178, 89, 36, 238, 174, 18, 234, 228, 26, 243, 232, 195, 162, 84, 35, 54, 136, 111, 68, 213, 199, 62, 202, 66, 2, 17, 0, 0, 0, 4, 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