Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4054cd9594daed5c0937cf528b2ac65db98fea0d730a92440c6d99c42e35e2b1

Tx prefix hash: be5cdd8c49ad12a3a8cf71df4e8cb6947edf189d3d6fdf83f185b16e65e9a35f
Tx public key: 1d7dd7be7eee8150a744a42e3ad057dcae43423829d13766f514f64cc548ef8e
Timestamp: 1745663919 Timestamp [UCT]: 2025-04-26 10:38:39 Age [y:d:h:m:s]: 00:015:03:50:46
Block: 1269815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10838 RingCT/type: yes/0
Extra: 011d7dd7be7eee8150a744a42e3ad057dcae43423829d13766f514f64cc548ef8e02110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a710f3db442153f6b4d5bacf679aa610d52d83a55372f644498198842f13bf40 0.600000000000 1757054 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": 1269825, "vin": [ { "gen": { "height": 1269815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a710f3db442153f6b4d5bacf679aa610d52d83a55372f644498198842f13bf40" } } ], "extra": [ 1, 29, 125, 215, 190, 126, 238, 129, 80, 167, 68, 164, 46, 58, 208, 87, 220, 174, 67, 66, 56, 41, 209, 55, 102, 245, 20, 246, 76, 197, 72, 239, 142, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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