Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f699505276941d3af7ad73773ff8d6ce4cf22ba4a0953b29c2167eb376e5048b

Tx prefix hash: ea0552df61e9871da0bd04e27cd433d2be62d04729f3774e781c298e51d42378
Tx public key: 431314e4a874265ecd797c976f162e1083d19f832fb99de9a88970ad5c478555
Timestamp: 1758090613 Timestamp [UCT]: 2025-09-17 06:30:13 Age [y:d:h:m:s]: 00:097:16:19:19
Block: 1370232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69932 RingCT/type: yes/0
Extra: 01431314e4a874265ecd797c976f162e1083d19f832fb99de9a88970ad5c478555021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3662dfa330f8b6e6173d25d08691b0f0cdc9790ace0652730d9d6fd8d57b9b38 0.600000000000 1858307 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": 1370242, "vin": [ { "gen": { "height": 1370232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3662dfa330f8b6e6173d25d08691b0f0cdc9790ace0652730d9d6fd8d57b9b38" } } ], "extra": [ 1, 67, 19, 20, 228, 168, 116, 38, 94, 205, 121, 124, 151, 111, 22, 46, 16, 131, 209, 159, 131, 47, 185, 157, 233, 168, 137, 112, 173, 92, 71, 133, 85, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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