Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355ba88a59dbd663ee45044bc08ed4cc7aad2a681f9052f23fd2d5680dd8df35

Tx prefix hash: a0ba49faa8d5ad91d6d68523b429594ee4f8e0e29723c5204e87dd566ee87b62
Tx public key: 9b0d89e7a5efbb7440496e176c11ee12e4c2dccee7130c13af32a26fc377af78
Timestamp: 1629198601 Timestamp [UCT]: 2021-08-17 11:10:01 Age [y:d:h:m:s]: 03:139:11:33:20
Block: 315919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872975 RingCT/type: yes/0
Extra: 019b0d89e7a5efbb7440496e176c11ee12e4c2dccee7130c13af32a26fc377af7802110000023c282c04e2000000000000000000

1 output(s) for total of 55.110866723000 dcy

stealth address amount amount idx
00: 346ee722b914f6fb5da12bfc42cec21eb3fd514dea80cbb0c4c1aab24ab6155b 55.110866723000 657366 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": 315929, "vin": [ { "gen": { "height": 315919 } } ], "vout": [ { "amount": 55110866723, "target": { "key": "346ee722b914f6fb5da12bfc42cec21eb3fd514dea80cbb0c4c1aab24ab6155b" } } ], "extra": [ 1, 155, 13, 137, 231, 165, 239, 187, 116, 64, 73, 110, 23, 108, 17, 238, 18, 228, 194, 220, 206, 231, 19, 12, 19, 175, 50, 162, 111, 195, 119, 175, 120, 2, 17, 0, 0, 2, 60, 40, 44, 4, 226, 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