Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7121cbb4fe9cc25e1366596cbd01474f41254b9037154cb486aa314b59992982

Tx prefix hash: 5900bda18836c0a7616f90a3fb1c81243e5eb6b94c90d67af1931292f2ba88be
Tx public key: 8f6a24bb03f32ebc73fbfcbb76d3a0c7619ea3a581ef647a65808732eb394c34
Timestamp: 1703492927 Timestamp [UCT]: 2023-12-25 08:28:47 Age [y:d:h:m:s]: 01:144:09:24:28
Block: 920705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364340 RingCT/type: yes/0
Extra: 018f6a24bb03f32ebc73fbfcbb76d3a0c7619ea3a581ef647a65808732eb394c34021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7c0cbd9f38e50b0da9ac57c581d0db6cad5cd9fcf402643cf4a1873d61f4fba 0.600000000000 1378387 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": 920715, "vin": [ { "gen": { "height": 920705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c0cbd9f38e50b0da9ac57c581d0db6cad5cd9fcf402643cf4a1873d61f4fba" } } ], "extra": [ 1, 143, 106, 36, 187, 3, 243, 46, 188, 115, 251, 252, 187, 118, 211, 160, 199, 97, 158, 163, 165, 129, 239, 100, 122, 101, 128, 135, 50, 235, 57, 76, 52, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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