Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64c50b85ea44244e839a712bfd6741a622e05eb8f9cd916436441de6aa9b117

Tx prefix hash: a03e264bb86e2915a76ea9dca5b77c4c3f948751fa1234858f0dd1655b470441
Tx public key: aabfb58dd19c9faccd3d591bac49fbed073622a9eb287982d316eba112d73c3b
Timestamp: 1693575500 Timestamp [UCT]: 2023-09-01 13:38:20 Age [y:d:h:m:s]: 01:219:18:03:31
Block: 838666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418167 RingCT/type: yes/0
Extra: 01aabfb58dd19c9faccd3d591bac49fbed073622a9eb287982d316eba112d73c3b02110000001d4b8f5122000000000000000000

1 output(s) for total of 1.021295618000 dcy

stealth address amount amount idx
00: da407a5dd570747ccfb2c095faf1d535ceb1427563ce3b5c6a9075fbb2a122a9 1.021295618000 1291434 of 0

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": 838676, "vin": [ { "gen": { "height": 838666 } } ], "vout": [ { "amount": 1021295618, "target": { "key": "da407a5dd570747ccfb2c095faf1d535ceb1427563ce3b5c6a9075fbb2a122a9" } } ], "extra": [ 1, 170, 191, 181, 141, 209, 156, 159, 172, 205, 61, 89, 27, 172, 73, 251, 237, 7, 54, 34, 169, 235, 40, 121, 130, 211, 22, 235, 161, 18, 215, 60, 59, 2, 17, 0, 0, 0, 29, 75, 143, 81, 34, 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