Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356e229b2bad77a472948162805054b7a82f996921c753d4f2ef73088f684226

Tx prefix hash: 63d8504aaa764f7a25d046404a97a6df5c2f69aa3df25e983fec70895107e2f7
Tx public key: b05a9acea13b8d4dfd691a3da0df7c9b5a9871e80ff4c0142b79031ce08766df
Timestamp: 1694835623 Timestamp [UCT]: 2023-09-16 03:40:23 Age [y:d:h:m:s]: 01:189:18:34:02
Block: 849119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396705 RingCT/type: yes/0
Extra: 01b05a9acea13b8d4dfd691a3da0df7c9b5a9871e80ff4c0142b79031ce08766df021100000004faf35c9c000000000000000000

1 output(s) for total of 0.943010058000 dcy

stealth address amount amount idx
00: 051d950af933cd22b33b8873b5f234969c5f33bc1d2db6abb053fb0b4dc3c228 0.943010058000 1302761 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": 849129, "vin": [ { "gen": { "height": 849119 } } ], "vout": [ { "amount": 943010058, "target": { "key": "051d950af933cd22b33b8873b5f234969c5f33bc1d2db6abb053fb0b4dc3c228" } } ], "extra": [ 1, 176, 90, 154, 206, 161, 59, 141, 77, 253, 105, 26, 61, 160, 223, 124, 155, 90, 152, 113, 232, 15, 244, 192, 20, 43, 121, 3, 28, 224, 135, 102, 223, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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