Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb3a5adc3c719f3c3da9d5de611402e9545fe0efda1fae79af1d38da4fb7e35f

Tx prefix hash: 18db5e99201f173dee2cba5a7e5a648562265c0f07d242a07bffad8234f3e63d
Tx public key: 1ca621b840d94b1f0a46802b8dc6cbb6b330192e8057329738123836babd640e
Timestamp: 1755385591 Timestamp [UCT]: 2025-08-16 23:06:31 Age [y:d:h:m:s]: 00:044:20:28:41
Block: 1348108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31813 RingCT/type: yes/0
Extra: 011ca621b840d94b1f0a46802b8dc6cbb6b330192e8057329738123836babd640e0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f160d803ddd9c3b4fe5cd0ed13dc27be323520537484efe924e2f652480134d3 0.600000000000 1836031 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": 1348118, "vin": [ { "gen": { "height": 1348108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f160d803ddd9c3b4fe5cd0ed13dc27be323520537484efe924e2f652480134d3" } } ], "extra": [ 1, 28, 166, 33, 184, 64, 217, 75, 31, 10, 70, 128, 43, 141, 198, 203, 182, 179, 48, 25, 46, 128, 87, 50, 151, 56, 18, 56, 54, 186, 189, 100, 14, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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