Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f5ae80731b244e2ba6cafe9808f9ce162ee4d0fb2b7546c456d01d4a4a7968

Tx prefix hash: d4885fb337188c8e3ad3bf1c6e4e79360d91b21e11993284503849d8ef0dfb97
Tx public key: cd25ab137f0507ca8a3e9ebaae4770ec56e2b47593efa1ad11e2a20317194852
Timestamp: 1704849616 Timestamp [UCT]: 2024-01-10 01:20:16 Age [y:d:h:m:s]: 01:301:09:23:30
Block: 931938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474204 RingCT/type: yes/0
Extra: 01cd25ab137f0507ca8a3e9ebaae4770ec56e2b47593efa1ad11e2a2031719485202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c099ec7d916060ff6868c418651d69b3773a179ffdc3c0cac35b953080791e0e 0.600000000000 1389846 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": 931948, "vin": [ { "gen": { "height": 931938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c099ec7d916060ff6868c418651d69b3773a179ffdc3c0cac35b953080791e0e" } } ], "extra": [ 1, 205, 37, 171, 19, 127, 5, 7, 202, 138, 62, 158, 186, 174, 71, 112, 236, 86, 226, 180, 117, 147, 239, 161, 173, 17, 226, 162, 3, 23, 25, 72, 82, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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