Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8933b6a161c118e5c461796efed23ad0df4843ed8a9cdbca162eb18cc6eec5c6

Tx prefix hash: 3dd065115503871550f135d18deffbb813d7d2a8b425f891765c2fdbc96e5266
Tx public key: 1ceecd4dbc67802daa58bac509827d8acdb5294b767614f8bf17e6a5b15bae4f
Timestamp: 1684604782 Timestamp [UCT]: 2023-05-20 17:46:22 Age [y:d:h:m:s]: 02:170:18:06:20
Block: 764367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641811 RingCT/type: yes/0
Extra: 011ceecd4dbc67802daa58bac509827d8acdb5294b767614f8bf17e6a5b15bae4f02110000000233af99f4000000000000000000

1 output(s) for total of 1.800259068000 dcy

stealth address amount amount idx
00: ab918b06b4ef6c9ce65b280a0c7ab9255c26d9b27cd549f0e2d2fb5339ffd783 1.800259068000 1213284 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": 764377, "vin": [ { "gen": { "height": 764367 } } ], "vout": [ { "amount": 1800259068, "target": { "key": "ab918b06b4ef6c9ce65b280a0c7ab9255c26d9b27cd549f0e2d2fb5339ffd783" } } ], "extra": [ 1, 28, 238, 205, 77, 188, 103, 128, 45, 170, 88, 186, 197, 9, 130, 125, 138, 205, 181, 41, 75, 118, 118, 20, 248, 191, 23, 230, 165, 177, 91, 174, 79, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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