Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944a4c351045f892fb3257ec5ca989e5009496e7db03badca57b357e0b17d1ca

Tx prefix hash: 40c32ce7ebf7a6e52df32b443e9f15113c77dbd9f9735a651c1c1c3eb3887bf7
Tx public key: 0000f9c24ed4fb3a88d3fe852b33d7d66272510400556e91d32baf811d458f57
Timestamp: 1729732723 Timestamp [UCT]: 2024-10-24 01:18:43 Age [y:d:h:m:s]: 00:161:19:44:35
Block: 1138209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115449 RingCT/type: yes/0
Extra: 010000f9c24ed4fb3a88d3fe852b33d7d66272510400556e91d32baf811d458f57021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1b034771bc0f4164ca08c7d3b24f7a9e02ce494efe61b00bbf831236712d010 0.600000000000 1621830 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": 1138219, "vin": [ { "gen": { "height": 1138209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1b034771bc0f4164ca08c7d3b24f7a9e02ce494efe61b00bbf831236712d010" } } ], "extra": [ 1, 0, 0, 249, 194, 78, 212, 251, 58, 136, 211, 254, 133, 43, 51, 215, 214, 98, 114, 81, 4, 0, 85, 110, 145, 211, 43, 175, 129, 29, 69, 143, 87, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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