Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb563a44c75b06a7a2cb987fd833d04ba0a6b33b4b2291195509d9181d96381e

Tx prefix hash: c1d778d2373c5f3ae1105c55a0d7a359d5fbcaec5cfbd2c22375ec4aa207691c
Tx public key: dd1545a7f2fea00ac50b33ba84d79116f01634bf0f4ae3d7d6f82ca0291707aa
Timestamp: 1763870899 Timestamp [UCT]: 2025-11-23 04:08:19 Age [y:d:h:m:s]: 00:045:10:50:34
Block: 1418139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32553 RingCT/type: yes/0
Extra: 01dd1545a7f2fea00ac50b33ba84d79116f01634bf0f4ae3d7d6f82ca0291707aa0211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49aff0b3234682cfd5fc8774146b1a00512ffde2c127389bb2c353f7a7c80d3 0.600000000000 1906666 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": 1418149, "vin": [ { "gen": { "height": 1418139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49aff0b3234682cfd5fc8774146b1a00512ffde2c127389bb2c353f7a7c80d3" } } ], "extra": [ 1, 221, 21, 69, 167, 242, 254, 160, 10, 197, 11, 51, 186, 132, 215, 145, 22, 240, 22, 52, 191, 15, 74, 227, 215, 214, 248, 44, 160, 41, 23, 7, 170, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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