Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396594b4917c1592e18f7184b0904d4279b46dc8e7037e410f7af8c549c5c99e

Tx prefix hash: 83f1e1179e9dcf4c7a8a1788749ec61548f7816328c9ddaf8a5abad274f42376
Tx public key: a195568f262d9a921b231fceb357b3034b9f3ebc51eb94545c7f65f62256fc5a
Timestamp: 1708441723 Timestamp [UCT]: 2024-02-20 15:08:43 Age [y:d:h:m:s]: 01:290:08:07:51
Block: 961729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466288 RingCT/type: yes/0
Extra: 01a195568f262d9a921b231fceb357b3034b9f3ebc51eb94545c7f65f62256fc5a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 143a6e1944c6532fb5fa6029be4994f055bff2c5e38a99996d2f0e0068b2adf8 0.600000000000 1421340 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": 961739, "vin": [ { "gen": { "height": 961729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "143a6e1944c6532fb5fa6029be4994f055bff2c5e38a99996d2f0e0068b2adf8" } } ], "extra": [ 1, 161, 149, 86, 143, 38, 45, 154, 146, 27, 35, 31, 206, 179, 87, 179, 3, 75, 159, 62, 188, 81, 235, 148, 84, 92, 127, 101, 246, 34, 86, 252, 90, 2, 17, 0, 0, 0, 4, 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