Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3589e35a66614dc2321ab9f3110e6edebf7c99a0fa7a2e04bdfdbc5401abef3

Tx prefix hash: 4544a1ac5e9bb63b0b2fb1fbef06522083be7f155269e50526911555e0c9ff4f
Tx public key: 189b7b70cc1c0b457b4810d17ff8bd3b814b9e12581b40e58d4e07039780cf32
Timestamp: 1751820312 Timestamp [UCT]: 2025-07-06 16:45:12 Age [y:d:h:m:s]: 00:130:17:31:07
Block: 1320047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91833 RingCT/type: yes/0
Extra: 01189b7b70cc1c0b457b4810d17ff8bd3b814b9e12581b40e58d4e07039780cf3202110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 328129db34c800b95a4cee7a1f7e70523c5d48ca29d1f07647d7d6416e6158fc 0.600000000000 1807742 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": 1320057, "vin": [ { "gen": { "height": 1320047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "328129db34c800b95a4cee7a1f7e70523c5d48ca29d1f07647d7d6416e6158fc" } } ], "extra": [ 1, 24, 155, 123, 112, 204, 28, 11, 69, 123, 72, 16, 209, 127, 248, 189, 59, 129, 75, 158, 18, 88, 27, 64, 229, 141, 78, 7, 3, 151, 128, 207, 50, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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