Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df046dfc4643e4f0d1a4f5b928ca99b3e3cdd72797515f1b79e642eabf04e43

Tx prefix hash: 7d225b10fb7598c289100236296a9e7cd7214af8e23bf1da3d56d68a3e8af706
Tx public key: 6e128d724b28b7236a9e61dde15a90f979a12291d85884839d32c538f76dc602
Timestamp: 1682376035 Timestamp [UCT]: 2023-04-24 22:40:35 Age [y:d:h:m:s]: 02:199:17:28:16
Block: 745887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 662589 RingCT/type: yes/0
Extra: 016e128d724b28b7236a9e61dde15a90f979a12291d85884839d32c538f76dc60202110000000175e3f0e9000000000000000000

1 output(s) for total of 2.072845561000 dcy

stealth address amount amount idx
00: e7fa364c9d1d13dce06bda188af4cd4f8825855d21558616db5550eea6cfbf08 2.072845561000 1193382 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": 745897, "vin": [ { "gen": { "height": 745887 } } ], "vout": [ { "amount": 2072845561, "target": { "key": "e7fa364c9d1d13dce06bda188af4cd4f8825855d21558616db5550eea6cfbf08" } } ], "extra": [ 1, 110, 18, 141, 114, 75, 40, 183, 35, 106, 158, 97, 221, 225, 90, 144, 249, 121, 161, 34, 145, 216, 88, 132, 131, 157, 50, 197, 56, 247, 109, 198, 2, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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