Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f890b9adcb2fb0855490dd13be243f4253b4c526285a28baeab1fc4cb91feb6b

Tx prefix hash: d61addcb4379b3df3ad8c702cacf244bbbc6a1930ae80060343367bb90daa8b1
Tx public key: 13e796e0b9c4b4674bac6457bf8ff36e8ce60396ba942736bce54812f90a2614
Timestamp: 1641129401 Timestamp [UCT]: 2022-01-02 13:16:41 Age [y:d:h:m:s]: 02:359:00:26:45
Block: 408889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774763 RingCT/type: yes/0
Extra: 0113e796e0b9c4b4674bac6457bf8ff36e8ce60396ba942736bce54812f90a2614021100000001a272b9cb000000000000000000

1 output(s) for total of 27.113235327000 dcy

stealth address amount amount idx
00: 027140e9050755bf99bd9442ea9ef8193ccc4a4bb99c5b76b417d4d8e03d41f2 27.113235327000 811166 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": 408899, "vin": [ { "gen": { "height": 408889 } } ], "vout": [ { "amount": 27113235327, "target": { "key": "027140e9050755bf99bd9442ea9ef8193ccc4a4bb99c5b76b417d4d8e03d41f2" } } ], "extra": [ 1, 19, 231, 150, 224, 185, 196, 180, 103, 75, 172, 100, 87, 191, 143, 243, 110, 140, 230, 3, 150, 186, 148, 39, 54, 188, 229, 72, 18, 249, 10, 38, 20, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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