Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4ca85ba4b9e84e0385f0efeb37f8487d59f599e67d99dcc9549041fc88c050e

Tx prefix hash: 52aff3375768148c8c9ca0aea545d38b08c758e17585a835770212f865e8fb63
Tx public key: af4b9d2a2f39347f6364f3720a85a6e515050e19ee98da5545fc6b361a903587
Timestamp: 1751020610 Timestamp [UCT]: 2025-06-27 10:36:50 Age [y:d:h:m:s]: 00:145:20:15:49
Block: 1313805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102261 RingCT/type: yes/0
Extra: 01af4b9d2a2f39347f6364f3720a85a6e515050e19ee98da5545fc6b361a903587021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef75b2f2b508c2462be10630a4a6baff4de4aaf5870a3f7a3d3f40b702fa840 0.600000000000 1801448 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": 1313815, "vin": [ { "gen": { "height": 1313805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef75b2f2b508c2462be10630a4a6baff4de4aaf5870a3f7a3d3f40b702fa840" } } ], "extra": [ 1, 175, 75, 157, 42, 47, 57, 52, 127, 99, 100, 243, 114, 10, 133, 166, 229, 21, 5, 14, 25, 238, 152, 218, 85, 69, 252, 107, 54, 26, 144, 53, 135, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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