Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26221ed48fa4dcc215911129930a41a0cea4773e0be746920ae7c8af29a79e5e

Tx prefix hash: 486b146fe8715ecd785b96b2a4768169b62bad969005043288d89e4ae3f5a4cf
Tx public key: 665f1f667bc044607676cd9a71cbea0e1e881df94b0595f871b0b80aa3d20931
Timestamp: 1764437124 Timestamp [UCT]: 2025-11-29 17:25:24 Age [y:d:h:m:s]: 00:035:08:31:42
Block: 1422841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25311 RingCT/type: yes/0
Extra: 01665f1f667bc044607676cd9a71cbea0e1e881df94b0595f871b0b80aa3d20931021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3ee4ca2d2282deee489a713ca1bcf9f972ff09430a9b1f7f3fcfa8eb02c3a2b 0.600000000000 1911414 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": 1422851, "vin": [ { "gen": { "height": 1422841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3ee4ca2d2282deee489a713ca1bcf9f972ff09430a9b1f7f3fcfa8eb02c3a2b" } } ], "extra": [ 1, 102, 95, 31, 102, 123, 192, 68, 96, 118, 118, 205, 154, 113, 203, 234, 14, 30, 136, 29, 249, 75, 5, 149, 248, 113, 176, 184, 10, 163, 210, 9, 49, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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