Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c0217f082f57cc3280a9cf80304b8e07fbf225d87d523caf1500ee4c82de01

Tx prefix hash: 04dd69091c73bfc2af7aa01d89b2ae2bb9b279a384aaf5ee371902b84c15ced0
Tx public key: fcba6f20548985e3e8bfbe0dcc3ed50e85d68fa6afb3d672d9a344642c1e6138
Timestamp: 1579220186 Timestamp [UCT]: 2020-01-17 00:16:26 Age [y:d:h:m:s]: 04:355:03:06:18
Block: 47145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143322 RingCT/type: yes/0
Extra: 01fcba6f20548985e3e8bfbe0dcc3ed50e85d68fa6afb3d672d9a344642c1e61380211000000014943cd9f000000000000000000

1 output(s) for total of 428.341231880000 dcy

stealth address amount amount idx
00: cb087b511e6fdb5db2fdcecd3c7a638867dc434b9f590b9a92762009d7eb36b9 428.341231880000 87102 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": 47155, "vin": [ { "gen": { "height": 47145 } } ], "vout": [ { "amount": 428341231880, "target": { "key": "cb087b511e6fdb5db2fdcecd3c7a638867dc434b9f590b9a92762009d7eb36b9" } } ], "extra": [ 1, 252, 186, 111, 32, 84, 137, 133, 227, 232, 191, 190, 13, 204, 62, 213, 14, 133, 214, 143, 166, 175, 179, 214, 114, 217, 163, 68, 100, 44, 30, 97, 56, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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