Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f0ad0ff28fa71e11dbafc562561e736740c1c676ff0eaf96a59d8e90494be3

Tx prefix hash: 00ecf3da29beab8bd0befc8127ccc06de816abfa0e3c884c760392c95b889c88
Tx public key: e9f6b0a4d7a1c263fb00047bda7a316322ada0e874309e0046c158e567feb5f1
Timestamp: 1703522343 Timestamp [UCT]: 2023-12-25 16:39:03 Age [y:d:h:m:s]: 01:112:18:25:10
Block: 920950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341718 RingCT/type: yes/0
Extra: 01e9f6b0a4d7a1c263fb00047bda7a316322ada0e874309e0046c158e567feb5f102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ed4d6d9ddc13ea558056fd3e41f91d976cbfe233026b1751af79ad6d07469fb 0.600000000000 1378634 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": 920960, "vin": [ { "gen": { "height": 920950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ed4d6d9ddc13ea558056fd3e41f91d976cbfe233026b1751af79ad6d07469fb" } } ], "extra": [ 1, 233, 246, 176, 164, 215, 161, 194, 99, 251, 0, 4, 123, 218, 122, 49, 99, 34, 173, 160, 232, 116, 48, 158, 0, 70, 193, 88, 229, 103, 254, 181, 241, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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