Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cd85aee7043a3c7140b50033527626d1a73b505b5d0f0922d82099d050aeadf

Tx prefix hash: a4e84cf6c2c5bd3e8857ff4f1e1aebc7ee2b444d02a7d6792540e559bf476cf4
Tx public key: b84bad731b69eb11ba205732e701383bed8a71de238c243af80e8dc520d0d9b4
Timestamp: 1578197595 Timestamp [UCT]: 2020-01-05 04:13:15 Age [y:d:h:m:s]: 05:103:16:29:26
Block: 38962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223989 RingCT/type: yes/0
Extra: 01b84bad731b69eb11ba205732e701383bed8a71de238c243af80e8dc520d0d9b40211000000108a2ee0d9000000000000000000

1 output(s) for total of 455.935668761000 dcy

stealth address amount amount idx
00: e85ad7a5c93dc10d6bb8a6174fce823f535a06eaa3b7f85c5ed7455f163ae2e3 455.935668761000 66817 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": 38972, "vin": [ { "gen": { "height": 38962 } } ], "vout": [ { "amount": 455935668761, "target": { "key": "e85ad7a5c93dc10d6bb8a6174fce823f535a06eaa3b7f85c5ed7455f163ae2e3" } } ], "extra": [ 1, 184, 75, 173, 115, 27, 105, 235, 17, 186, 32, 87, 50, 231, 1, 56, 59, 237, 138, 113, 222, 35, 140, 36, 58, 248, 14, 141, 197, 32, 208, 217, 180, 2, 17, 0, 0, 0, 16, 138, 46, 224, 217, 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