Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62044640ed10f619c53f58117b7c33e7ed8a7bbabb62fbb06fa1a504464da67

Tx prefix hash: 381385a29edcc02dccc5e044358f180cda4cba9d2e767d52b6f3d8215b2b8b1f
Tx public key: a0f98b8cc85f62a361c3d3321ec1ea086eb88e966c86cbe5c321757936b8eefe
Timestamp: 1743098477 Timestamp [UCT]: 2025-03-27 18:01:17 Age [y:d:h:m:s]: 00:045:03:04:56
Block: 1248550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32298 RingCT/type: yes/0
Extra: 01a0f98b8cc85f62a361c3d3321ec1ea086eb88e966c86cbe5c321757936b8eefe021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b626354656e95dfdd07c441a0cd9853cb6dd1ec8ad0dc41ec9ef7434fc21624 0.600000000000 1735583 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": 1248560, "vin": [ { "gen": { "height": 1248550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b626354656e95dfdd07c441a0cd9853cb6dd1ec8ad0dc41ec9ef7434fc21624" } } ], "extra": [ 1, 160, 249, 139, 140, 200, 95, 98, 163, 97, 195, 211, 50, 30, 193, 234, 8, 110, 184, 142, 150, 108, 134, 203, 229, 195, 33, 117, 121, 54, 184, 238, 254, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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