Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c28194bfcf3fe3548c239e7eb08b99704b9ac605d25804db5074dc4038b5861

Tx prefix hash: 2e7a34c68d45cd997d16e2ea06504c4ccedb139397aafc745bfb995d1f1d5280
Tx public key: c96a5fa3d6e583eea342c283323ae5713a3ac908190e2846efea303a1aa45903
Timestamp: 1758098617 Timestamp [UCT]: 2025-09-17 08:43:37 Age [y:d:h:m:s]: 00:112:21:15:23
Block: 1370298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80835 RingCT/type: yes/0
Extra: 01c96a5fa3d6e583eea342c283323ae5713a3ac908190e2846efea303a1aa45903021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bc2f7a3124f90f201462976e48fb842d088846359722f2799fd18b969c57a1d 0.600000000000 1858373 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": 1370308, "vin": [ { "gen": { "height": 1370298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bc2f7a3124f90f201462976e48fb842d088846359722f2799fd18b969c57a1d" } } ], "extra": [ 1, 201, 106, 95, 163, 214, 229, 131, 238, 163, 66, 194, 131, 50, 58, 229, 113, 58, 58, 201, 8, 25, 14, 40, 70, 239, 234, 48, 58, 26, 164, 89, 3, 2, 17, 0, 0, 0, 7, 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