Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f2b16736ba62d1b23949b219f1a7e0590bc95ed0a1d210bb22e7096c9f36d5

Tx prefix hash: 648a9b3e81f946fdfa921f02ed3479b40e4413004ec7817385d51ef80b2b900e
Tx public key: de92175c615e1853c21e0639d19f2059ed834d8c855f837a0ffaebd8d2680ef8
Timestamp: 1711661158 Timestamp [UCT]: 2024-03-28 21:25:58 Age [y:d:h:m:s]: 01:224:07:40:28
Block: 988437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418993 RingCT/type: yes/0
Extra: 01de92175c615e1853c21e0639d19f2059ed834d8c855f837a0ffaebd8d2680ef802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20833e1da7c1bcd54c32af5da2c36e69e3b8ecdd6fd93d1fd6ee992df0e5e338 0.600000000000 1448716 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": 988447, "vin": [ { "gen": { "height": 988437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20833e1da7c1bcd54c32af5da2c36e69e3b8ecdd6fd93d1fd6ee992df0e5e338" } } ], "extra": [ 1, 222, 146, 23, 92, 97, 94, 24, 83, 194, 30, 6, 57, 209, 159, 32, 89, 237, 131, 77, 140, 133, 95, 131, 122, 15, 250, 235, 216, 210, 104, 14, 248, 2, 17, 0, 0, 0, 1, 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