Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 757ef3b5de72f65a89b11cdf60b2dccc2dfa513515f6142968c305362af07048

Tx prefix hash: c9750727a14d90d07e5a0da7f17aa5b685ca43a21fb2d0c1e674d4121e7d1fe0
Tx public key: 2f2bd82f3e968a059828727456607d41be62b0ce310b510c3d309338f622cea6
Timestamp: 1757006309 Timestamp [UCT]: 2025-09-04 17:18:29 Age [y:d:h:m:s]: 00:075:16:19:48
Block: 1361318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54114 RingCT/type: yes/0
Extra: 012f2bd82f3e968a059828727456607d41be62b0ce310b510c3d309338f622cea6021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c280d79e2f33e2d39fba437133262f09dea094e3dfbc702c3e908fff42488ea5 0.600000000000 1849331 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": 1361328, "vin": [ { "gen": { "height": 1361318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c280d79e2f33e2d39fba437133262f09dea094e3dfbc702c3e908fff42488ea5" } } ], "extra": [ 1, 47, 43, 216, 47, 62, 150, 138, 5, 152, 40, 114, 116, 86, 96, 125, 65, 190, 98, 176, 206, 49, 11, 81, 12, 61, 48, 147, 56, 246, 34, 206, 166, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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