Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a248753121241fff906298374d7097d30a257f1126ac9e232534f49f98fc1504

Tx prefix hash: 316028264b8dcb0975594b3321619d9b22fe7e356b07ed9177243af7d06e85d6
Tx public key: 64770b3537a41e9bc2fd75f50e9ce9e284d08a0e8da4d60eecae76de92ab4639
Timestamp: 1687751292 Timestamp [UCT]: 2023-06-26 03:48:12 Age [y:d:h:m:s]: 01:244:00:49:29
Block: 790461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435518 RingCT/type: yes/0
Extra: 0164770b3537a41e9bc2fd75f50e9ce9e284d08a0e8da4d60eecae76de92ab46390211000000034b8f5122000000000000000000

1 output(s) for total of 1.475280883000 dcy

stealth address amount amount idx
00: ca161c6bc9a1eac13da93972e3d7afc7cfc31d1dc195d51c0d230ca7d6260727 1.475280883000 1240806 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": 790471, "vin": [ { "gen": { "height": 790461 } } ], "vout": [ { "amount": 1475280883, "target": { "key": "ca161c6bc9a1eac13da93972e3d7afc7cfc31d1dc195d51c0d230ca7d6260727" } } ], "extra": [ 1, 100, 119, 11, 53, 55, 164, 30, 155, 194, 253, 117, 245, 14, 156, 233, 226, 132, 208, 138, 14, 141, 164, 214, 14, 236, 174, 118, 222, 146, 171, 70, 57, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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