Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f48d5415aae1c99ef1d01e86efe94f87c1817bc1b3838e682a460d565660af

Tx prefix hash: 54273e7771fa87e457dc5ac6851a2bf1b90d3cfdea4d0500ea1f9b6764c193ae
Tx public key: ae8092d263c72cc8e3602881ef84daac9b658be10f1546cc27b3465c725b703b
Timestamp: 1759763298 Timestamp [UCT]: 2025-10-06 15:08:18 Age [y:d:h:m:s]: 00:094:20:49:39
Block: 1384094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67935 RingCT/type: yes/0
Extra: 01ae8092d263c72cc8e3602881ef84daac9b658be10f1546cc27b3465c725b703b021100000008a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dbfc4ebe40b8990e1cdec131eae4e460063aba3be0aae38e151f32e53d1f642 0.600000000000 1872243 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": 1384104, "vin": [ { "gen": { "height": 1384094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dbfc4ebe40b8990e1cdec131eae4e460063aba3be0aae38e151f32e53d1f642" } } ], "extra": [ 1, 174, 128, 146, 210, 99, 199, 44, 200, 227, 96, 40, 129, 239, 132, 218, 172, 155, 101, 139, 225, 15, 21, 70, 204, 39, 179, 70, 92, 114, 91, 112, 59, 2, 17, 0, 0, 0, 8, 165, 220, 205, 121, 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